stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2024-03-28T10:17:29Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/1350Make RADIUS-related sytem tests compatible with Kea 2.52024-03-28T10:17:29ZSlawek FigielMake RADIUS-related sytem tests compatible with Kea 2.5Upgrading Kea in system tests to the 2.5 version caused a system test failure that involved RADIUS. Kea team is working on RADIUS changes which apparently has changed in 2.5.
It blocks us from upgrading Kea in system tests and writing t...Upgrading Kea in system tests to the 2.5 version caused a system test failure that involved RADIUS. Kea team is working on RADIUS changes which apparently has changed in 2.5.
It blocks us from upgrading Kea in system tests and writing the system tests for the hub-and-spoke feature.https://gitlab.isc.org/isc-projects/stork/-/issues/1349HA panel should use Stork-style machine naming2024-03-28T10:07:06ZSlawek FigielHA panel should use Stork-style machine namingPlease use the machine name in the application identifier. It should be: `kea@agent-kea-ha1` and `kea@agent-kea-ha3` instead of `Kea@127.0.0.1`. We usually use this convention in Stork.
Current:
![image](/uploads/7e083489c97d5ff8d60d4...Please use the machine name in the application identifier. It should be: `kea@agent-kea-ha1` and `kea@agent-kea-ha3` instead of `Kea@127.0.0.1`. We usually use this convention in Stork.
Current:
![image](/uploads/7e083489c97d5ff8d60d469699eb380a/image.png)
After #1274 merge:
![image](/uploads/7a22035e53f32a1544235987e84cad8f/image.png)https://gitlab.isc.org/isc-projects/stork/-/issues/1348Remove stork-repo tag from .gitlab-ci.yaml2024-03-27T16:57:15ZSlawek FigielRemove stork-repo tag from .gitlab-ci.yamlThe `upload_to_repo` CI task is not working as described [on MM QA channel](https://mattermost.isc.org/isc/pl/eoq3yfamnbfz7n6tfaewdmc6mh).
We got this error:
> This job is stuck because of one of the following problems. There are no ac...The `upload_to_repo` CI task is not working as described [on MM QA channel](https://mattermost.isc.org/isc/pl/eoq3yfamnbfz7n6tfaewdmc6mh).
We got this error:
> This job is stuck because of one of the following problems. There are no active runners online, no runners for the protected branch, or no
runners that match all of the job's tags:
Its tags defined in the .gitlab-ci.yml file are:
- linux
- aws
- runner-manager
- amd64
- stork-repo
I checked the Stork repository settings and it seems there is no runner that matches the requirements.
The `aws` tag is missing in all runners that have the stork-repo tag.
### Proposed solution:
* remove `stork-repo` tag from `upload_to_repo` job in .gitlab-ci.yml.
* remove `-4` (which enforces IPv4 connection) from `ssh-keyscan -4 repo.isc.org >> ~/.ssh/known_hosts`https://gitlab.isc.org/isc-projects/stork/-/issues/13471.15.1 Clean up2024-03-28T09:04:35ZMarcin Godzina1.15.1 Clean upThings to do after 1.15.1 release:
- [ ] Move private code to public repository
- [ ] Mark [Tag](https://gitlab.isc.org/isc-projects/stork/-/tags) and [Release](https://gitlab.isc.org/isc-projects/stork/-/releases) in Repository
- [ ] R...Things to do after 1.15.1 release:
- [ ] Move private code to public repository
- [ ] Mark [Tag](https://gitlab.isc.org/isc-projects/stork/-/tags) and [Release](https://gitlab.isc.org/isc-projects/stork/-/releases) in Repository
- [ ] Rebuild Read The Docks (It can not pull from a private repository.)
- [ ] Fix `upload_to_repo` and `upload_to_repo_hooks` jobs/runners problem https://gitlab.isc.org/isc-projects/stork/-/issues/1348 https://gitlab.isc.org/isc-projects/stork/-/issues/13121.16https://gitlab.isc.org/isc-projects/stork/-/issues/1342Agent installation script doesn't work with stork configured for https2024-03-27T10:50:22Zjerry bonnerAgent installation script doesn't work with stork configured for https---
name: Bug report
about: Create a report to help us improve
---
If you believe your bug report is a security issue (e.g. a packet that can kill the server), DO NOT
REPORT IT HERE. Please use https://www.isc.org/community/report-bug/...---
name: Bug report
about: Create a report to help us improve
---
If you believe your bug report is a security issue (e.g. a packet that can kill the server), DO NOT
REPORT IT HERE. Please use https://www.isc.org/community/report-bug/ instead or send mail to
security-office(at)isc(dot)org.
**Describe the bug**
Stork 1.15.0 configured with https. Agent installation script from GUI details :
wget https://x.x.x.x:8080/stork-install-agent.sh
However, stork-install-agent.sh is configured to download package via :
curl -o /tmp/isc-stork-agent.deb "x.x.x.x:8080/assets/pkgs/isc-stork-agent_1.15.0.240205220739_amd64.deb"
Note that "https://" is not specified.
Resulting in a downloaded file that contains:
Client sent an HTTP request to an HTTPS server.
**To Reproduce**
Steps to reproduce the behavior:
1. Install Stork 1.15.0 and configure with https
2. Execute provided agent installation from GUI
3. Script fails because isc stork agent package is attempted to be downloaded via http, but stork is configured with https
**Expected behavior**
Stork should code agent installation script to download asset package via https, if STORK_REST_TLS_CERTIFICATE is configured.
**Environment:**
- Stork: 1.15.0
- OS: Ubuntu 20.04https://gitlab.isc.org/isc-projects/stork/-/issues/1341Add a reference from the Stork ARM to the KB on how to generate the certifica...2024-03-28T10:29:47ZMarcin SiodelskiAdd a reference from the Stork ARM to the KB on how to generate the certificates?We have created KB on how to generate and import the certificates to Stork. I wonder if we maybe need to give a link from the Stork ARM to this article?We have created KB on how to generate and import the certificates to Stork. I wonder if we maybe need to give a link from the Stork ARM to this article?1.16https://gitlab.isc.org/isc-projects/stork/-/issues/1337reservations without an IP do not show up in host reservations2024-03-27T18:24:20Zmichael balesreservations without an IP do not show up in host reservations---
name: reservations without an IP do not show up in host reservations
about: Create a report to help us improve
---
If you believe your bug report is a security issue (e.g. a packet that can kill the server), DO NOT
REPORT IT HERE. ...---
name: reservations without an IP do not show up in host reservations
about: Create a report to help us improve
---
If you believe your bug report is a security issue (e.g. a packet that can kill the server), DO NOT
REPORT IT HERE. Please use https://www.isc.org/community/report-bug/ instead or send mail to
security-office(at)isc(dot)org.
**Describe the bug**
Stork allows the creation of reservations with just a mac address and client class but the reservation does not show up in the host reservation list.
**To Reproduce**
Steps to reproduce the behavior:
1. Install BIND9, Kea, Stork (which versions?) and run them with the following configs: '...'
2. I do the following: ...
3. A device in my network does the following: ...
4. Kea/BIND9 server does the following: ...
5. Stork does the following: ...
**Expected behavior**
A clear and concise description of what you expected to happen:
The Stork is supposed to report/do A, but didn't or did B instead.
**Environment:**
- Kea version:
2.5.6
isc20240226130228 deb
linked with:
log4cplus 2.0.5
OpenSSL 3.0.2 15 Mar 2022
database:
MySQL backend 21.0, library 8.0.36
PostgreSQL backend 20.0, library 140011
Memfile backend 3.0
- Stork: 1.15.0
- OS: Ubuntu 22.04.4 LTS x86_64
- Kea: "hooks-libraries": [
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_stat_cmds.so"
},
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so"
},
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_pgsql_cb.so"
},
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_host_cmds.so"
}
**Additional Information**
logs from adding the reservation:
```
082 17:40:10.417 kea-dhcp4.commands COMMAND_SOCKET_CONNECTION_OPENED Opened socket 37 for incoming command connection
082 17:40:10.417 kea-dhcp4.commands COMMAND_SOCKET_READ Received 212 bytes over command socket 37
082 17:40:10.418 kea-dhcp4.commands COMMAND_RECEIVED Received command 'reservation-add'
082 17:40:10.418 kea-dhcp4.callouts HOOKS_CALLOUTS_BEGIN begin all callouts for hook $reservation_add
082 17:40:10.418 kea-dhcp4.host-cmds-hooks HOST_CMDS_RESERV_ADD reservation-add command called (parameters: { "reservation": { "client-classes": [ "known-clients-106" ], "hw-address": "C03EBA93B18D", "subnet-id": 3 } })
082 17:40:10.418 kea-dhcp4.database DATABASE_PGSQL_START_TRANSACTION starting a new PostgreSQL transaction
082 17:40:10.422 kea-dhcp4.database DATABASE_PGSQL_COMMIT committing to PostgreSQL database
082 17:40:10.423 kea-dhcp4.host-cmds-hooks HOST_CMDS_RESERV_ADD_SUCCESS reservation-add command success (parameters: { "reservation": { "client-classes": [ "known-clients-106" ], "hw-address": "C03EBA93B18D", "subnet-id": 3 } })
082 17:40:10.423 kea-dhcp4.callouts HOOKS_CALLOUT_CALLED hooks library with index 4 has called a callout on hook $reservation_add that has address 0x7ff4efd4e900 (callout duration: 5.567 ms)
082 17:40:10.423 kea-dhcp4.callouts HOOKS_CALLOUTS_COMPLETE completed callouts for hook $reservation_add (total callouts duration: 5.567 ms)
082 17:40:10.423 kea-dhcp4.commands COMMAND_SOCKET_WRITE Sent response of 38 bytes (0 bytes left to send) over command socket 37
082 17:40:10.423 kea-dhcp4.commands COMMAND_SOCKET_CONNECTION_CLOSED Closed socket 37 for existing command connection
```
after the reservation is added the reservation list in stork does not show the mac address or hostname
**Describe the solution you'd like*
Reservations without an assigned IP address should show the hostname and mac address in the reservation list.
**Additional context**
We use small DHCP pools of 20 or so addresses so handle mobile devices that are occasionally connected to the network. We managed this with isc-dhcpd previously by using global reservations with just a mac address. It looks like in isc-kea a mac address and a resource are required and my understanding is that a client class counts as a resource so the reservation should be valid. Instead of global reservations we are now using per subnet reservations.
**Funding its development**
Kea is run by ISC, which is a small non-profit organization without any government funding or any
permanent sponsorship organizations. Are you able and willing to participate financially in the
development costs?
Yes this is a possibility
**Participating in development**
Are you willing to participate in the feature development? ISC team always tries to make a feature
as generic as possible, so it can be used in wide variety of situations. That means the proposed
solution may be a bit different that you initially thought. Are you willing to take part in the
design discussions? Are you willing to test an unreleased engineering code?
Yes i am willing to participate in development.
**Contacting you**
How can ISC reach you to discuss this matter further? If you do not specify any means such as
e-mail, jabber id or a telephone, we may send you a message on github with questions when we have
them.1.17https://gitlab.isc.org/isc-projects/stork/-/issues/1336Stork-Server is confused by multiple Kea DHCP versions installed2024-03-26T11:25:44ZCarsten StrotmannStork-Server is confused by multiple Kea DHCP versions installed---
name: Bug report
about: Create a report to help us improve
---
**Describe the bug**
Stork-Server (or Stork-Agent) is confused by multiple Kea-DHCP versions installed on the same machine and displays inconsistent version number.
On...---
name: Bug report
about: Create a report to help us improve
---
**Describe the bug**
Stork-Server (or Stork-Agent) is confused by multiple Kea-DHCP versions installed on the same machine and displays inconsistent version number.
On my (testing) system, I have the OS delivered Kea-DHCP (version 2.4.1 from Fedora 39) as well as a Kea-DHCP version (2.5.6 installed from source). The Version 2.4.1 is "in path" (/usr/bin:/usr/sbin) but not running, whereas 2.5.6 is not "in path" (/opt/kea/sbin), but "is" running.
Stork does display both versions numbers:
![Stork-Kea-Version-Number02.png](/uploads/9b5291671228bdb67c5c6c799278fe59/Stork-Kea-Version-Number02.png)
![Stork-Kea-Version-Number01.png](/uploads/ad42cf27202a4f5a91463da2ef91a88b/Stork-Kea-Version-Number01.png)
**To Reproduce** Steps to reproduce the behavior:
1. two different versions of Kea DHCP, Stork Agent and Stork Server
2. check the Kea Version numbers in the Stork Web-UI
**Expected behavior**
Show the running Kea-DHCP version number all the time.https://gitlab.isc.org/isc-projects/stork/-/issues/1335Not possible to run DHCPv6 only and collect stats with Prometheus2024-03-25T17:24:07ZRinse KloekNot possible to run DHCPv6 only and collect stats with Prometheus - Kea version: 2.4.1
- Stork: which version? 1.15.0
- OS: Debian 11
I have an issue with the prometheus exporter. I had enabled DHCPv4/DHCPv6/D2 in my kea-ctrl-agent as well as installed the KEA DHCPv4 server. However this server on... - Kea version: 2.4.1
- Stork: which version? 1.15.0
- OS: Debian 11
I have an issue with the prometheus exporter. I had enabled DHCPv4/DHCPv6/D2 in my kea-ctrl-agent as well as installed the KEA DHCPv4 server. However this server only serves DHCPv6 request. If I remove the DHCPv6/D2 entries in the Kea-ctrl-agent.conf and deinstall KEA DHCPv4 server, I am not able to see my DHCPv6 PD stats (kea_dhcp6_pd_assigned_total) anymore.
I get this error message in the log on the server
stork-agent[929757]: time="2024-03-19 11:54:23" level="error" msg="Problem parsing DHCPv4 labels from Kea: problem with content of DHCP labels response from Kea: forwarding socket is not configured for the server type dhcp4\nisc.org/stork/agent.(*SubnetList).UnmarshalJSON\n\t/builds/isc-projects/stork/backend/agent/promkeaexporter.go:82\nencoding/json.(*decodeState).array\n\t/builds/isc-projects/stork/tools/golang/go/src/encoding/json/decode.go:507\nencoding/json.(*decodeState).value\n\t/builds/isc-projects/stork/tools/golang/go/src/encoding/json/decode.go:364\nencoding/json.(*decodeState).unmarshal\n\t/builds/isc-projects/stork/tools/golang/go/src/encoding/json/decode.go:181\nencoding/json.Unmarshal\n\t/builds/isc-projects/stork/tools/golang/go/src/encoding/json/decode.go:108\nisc.org/stork/agent.(*lazySubnetNameLookup).fetchAndCacheNames\n\t/builds/isc-projects/stork/backend/agent/promkeaexporter.go:274\nisc.org/stork/agent.(*lazySubnetNameLookup).getName\n\t/builds/isc-projects/stork/backend/agent/promkeaexporter.go:291\nisc.org/stork/agent.(*lazySubnetNameLookup).getNameOrDefault\n\t/builds/isc-projects/stork/backend/agent/promkeaexporter.go:303\nisc.org/stork/agent.(*PromKeaExporter).setDaemonStats\n\t/builds/isc-projects/stork/backend/agent/promkeaexporter.go:772\nisc.org/stork/agent.(*PromKeaExporter).collectStats\n\t/builds/isc-projects/stork/backend/agent/promkeaexporter.go:877\nisc.org/stork/agent.(*PromKeaExporter).statsCollectorLoop\n\t/builds/isc-projects/stork/backend/agent/promkeaexporter.go:724\nruntime.goexit\n\t/builds/isc-projects/stork/tools/golang/go/src/runtime/asm_amd64.s:1650" file=" promkeaexporter.go:276 "
`
After installing the KEA DHCPv4 server again and reeneabling the KEA DHCPv4 server in kea-ctrl-agent these log message don't appear anymore and the Prometheus stats collection works again.
Is it possible to remove the DHCPv4 server and keep the stats working for DHCPv6
regads,
Rinsehttps://gitlab.isc.org/isc-projects/stork/-/issues/1333Incorrect error handing of the bind9 app state causes no transition to the in...2024-03-14T12:23:22ZMarcin SiodelskiIncorrect error handing of the bind9 app state causes no transition to the inactive stateThe `GetAppState()` logic returns early when communication with named fails. As a result, the info about the app is not updated in the database. So, for example, the active flag remains true, while it should be put to false. The daemon a...The `GetAppState()` logic returns early when communication with named fails. As a result, the info about the app is not updated in the database. So, for example, the active flag remains true, while it should be put to false. The daemon appears to be online in the UI even though there is no connection to it.https://gitlab.isc.org/isc-projects/stork/-/issues/1331Change the protobuf field names to follow the naming convention2024-03-19T14:59:57ZSlawek FigielChange the protobuf field names to follow the naming conventionThe field names should be written using the `snake_case`. We use `camelCase`.
It causes the generated GRPC API files for non-Go languages not to follow the expected naming conventions.
```
message GetStateRsp {
string agentVersion = 1...The field names should be written using the `snake_case`. We use `camelCase`.
It causes the generated GRPC API files for non-Go languages not to follow the expected naming conventions.
```
message GetStateRsp {
string agentVersion = 1;
repeated App apps = 2;
string hostname = 3;
int64 cpus = 4;
string cpusLoad = 5;
int64 memory = 6;
int64 usedMemory = 7;
int64 uptime = 8;
string error = 9;
string os = 10;
string platform = 11;
string platformFamily = 12;
string platformVersion = 13;
string kernelVersion = 14;
string kernelArch = 15;
string virtualizationSystem = 16;
string virtualizationRole = 17;
string hostID = 18;
bool agentUsesHTTPCredentials = 19;
}
```
References: https://protobuf.dev/programming-guides/style/#message-field-namesbackloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1329Event-driven HA status monitoring2024-03-26T14:55:35ZMarcin SiodelskiEvent-driven HA status monitoringCurrently we poll every 10s for the current HA state. I'd like to suggest that we move to an event-based monitoring where the changes will be signaled by the server to the subscribers over SSE. This should reduce the amount of processing...Currently we poll every 10s for the current HA state. I'd like to suggest that we move to an event-based monitoring where the changes will be signaled by the server to the subscribers over SSE. This should reduce the amount of processing in the browser and should cause an immediate reaction to the HA state changes.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1326Stork does not display leases statistics2024-03-14T14:07:08ZJohn PapStork does not display leases statistics**Describe the bug**
Stork server not displaying lease statistics. Remote stork agent has already registered. Stork server GUI displays the kea dhcp4 service correctly and I can manually pull statistics via the API from the stork server'...**Describe the bug**
Stork server not displaying lease statistics. Remote stork agent has already registered. Stork server GUI displays the kea dhcp4 service correctly and I can manually pull statistics via the API from the stork server's CLI using curl. Although there are active leases for clients the Web UI displays 0 for assigned IPs on all subnets. Probably a bug in the stat-lease4-get API command.
**To Reproduce**
Steps to reproduce the behavior:
1. Install Kea server 2.0.2, Stork 1.15.0 and run them with the following configs: '...'
2. Configure several subnets.
2. Have 3 VMs act as clients on all subnets and get ip addresses from kea server
3. Clients get IP address but the Stork GUI shows 0 for all lease statistics.
**Expected behavior**
Stork GUI should display the leases statistics for the connected clients.
**Environment:**
- Kea version: 2.0.2
- Stork: 1.15.0
- OS: Ubuntu 22.04 x64
- Kea: Hooks libdhcp_stat_cmds.so, libdhcp_lease_cmds.so
**Additional Information**
Querying the DHCP agent from the stork server using the cli and the management API I figured out that the stat-lease4-get command without arguments returns different results for the same subnet than the stat-lease4-get command having the subnet-id as an argument.
curl -X POST -H "Content-Type: application/json" -d '{ "command": "stat-lease4-get", "service": ["dhcp4"]}' http://192.168.59.21:8000
[ { "arguments": { "result-set": { "columns": [ "subnet-id", "total-addresses", "cumulative-assigned-addresses", "assigned-addresses", "declined-addresses" ], "rows": [ [ 47, 56, 0, 0, 0 ], [ 51, 56, 0, 0, 0 ], [ 66, 41, 0, 0, 0 ] ], "timestamp": "2024-03-08 14:09:09.100431" } }, "result": 0, "text": "stat-lease4-get[all subnets]: 3 rows found" } ]
curl -X POST -H "Content-Type: application/json" -d '{ "command": "stat-lease4-get", "service": ["dhcp4"], "arguments": {"subnet-id" : 66}}' http://192.168.59.21:8000
[ { "arguments": { "result-set": { "columns": [ "subnet-id", "total-addresses", "cumulative-assigned-addresses", "assigned-addresses", "declined-addresses" ], "rows": [ [ 66, 41, 0, 3, 0 ] ], "timestamp": "2024-03-08 14:09:17.884123" } }, "result": 0, "text": "stat-lease4-get[subnet-id=66]: 1 rows found" } ]
The second output above has the correct leases stats for subnet-id 66 while the first output shows 0 leases for subnet-id 66https://gitlab.isc.org/isc-projects/stork/-/issues/1325LDAP hook: Different DNs for bind user and login users2024-03-26T14:54:08ZRobin BergerLDAP hook: Different DNs for bind user and login usersIf your bind user has a different `dn` than the users that will be able to login to the stork web interface, you don't have a chance to set different root `dn`s.
Here a example:
Bind user: cn=bind_user,ou=service_account,ou=users,dc=ex...If your bind user has a different `dn` than the users that will be able to login to the stork web interface, you don't have a chance to set different root `dn`s.
Here a example:
Bind user: cn=bind_user,ou=service_account,ou=users,dc=example,dc=org
Login user: cn=login_user,ou=real_users,ou=users,dc=example,dc=org
It tried to use the maximum similar `dn` as root parameter and set the remainder in the bind username variable like this:
```
STORK_SERVER_HOOK_LDAP_ROOT="ou=users,dc=example,dc=org"
STORK_SERVER_HOOK_LDAP_BIND_USERNAME="bind_user,ou=service_account"
```
With this setup I was able to get the connection to ldap with the bind user but I was not able to login with a user, becuause I was not able to manipulate the username like the `STORK_SERVER_HOOK_LDAP_BIND_USERNAME` variable.
---
A possible solution is to set the full dn for the bind user in `STORK_SERVER_HOOK_LDAP_BIND_USERNAME` and use the `STORK_SERVER_HOOK_LDAP_ROOT` only for the search base of the users that will be able to login to the web interface.
Although I am not very comfortable with go and ldap, I would be able to help in implementing this solution.1.17https://gitlab.isc.org/isc-projects/stork/-/issues/1324502 bad gateway on authorize kea machine, but it is visible in authorized mac...2024-03-26T14:53:23ZPiotrek Zadroga502 bad gateway on authorize kea machine, but it is visible in authorized machines afterThis issue happened to me while running stork demo.
I tried to authorize 2 kea machines: `agent-kea6` and `agent-kea`.
The latter couldn't be authorized, I got 502 error.
Request:
```
XHRPUT
http://127.0.0.1:8080/api/machines/8
[HTTP/1...This issue happened to me while running stork demo.
I tried to authorize 2 kea machines: `agent-kea6` and `agent-kea`.
The latter couldn't be authorized, I got 502 error.
Request:
```
XHRPUT
http://127.0.0.1:8080/api/machines/8
[HTTP/1.1 502 Bad Gateway 280ms]
```
```json
{"address":"agent-kea","agentPort":8888,"agentToken":"(...)","apps":[],"id":8,"authorized":true}
```
But the machine disappeared from unauthorized machines and appeared in authorized:
![image](/uploads/bea9bebfe8ead8a60aec4790e80e2344/image.png)
I also got some 502's and 504's in console after:
![image](/uploads/fc99562530d9e658c84f700bf11f3134/image.png)1.17https://gitlab.isc.org/isc-projects/stork/-/issues/1323Attach more labels to the Prometheus samples2024-03-19T14:58:05ZSlawek FigielAttach more labels to the Prometheus samplesCurrently, if you haven't the subnet_cmds hook, the metrics are labeled with the subnet ID, and if you have the subnet_cmds hook, the metrics are labeled with the subnet name prefix if provided, otherwise with the subnet ID.
Our custome...Currently, if you haven't the subnet_cmds hook, the metrics are labeled with the subnet ID, and if you have the subnet_cmds hook, the metrics are labeled with the subnet name prefix if provided, otherwise with the subnet ID.
Our customer needs samples labeled by subnet ID regardless of the subnet_cmds presence. It would also be helpful to attach the shared network name.
[SF#1762](https://isc.lightning.force.com/lightning/r/Case/500S6000006AQSSIA4/view)1.17https://gitlab.isc.org/isc-projects/stork/-/issues/1322Upgrade Grafana and its dashboards2024-03-05T15:02:12ZSlawek FigielUpgrade Grafana and its dashboardsYou cannot import the example Grafana dashboards to a modern Grafana instance.
![image](/uploads/a95f33a1aa876ae18d92057fd933fc5f/image.png)
The Stork demo uses the `8.3.7` Grafana version. The latest version is `10.3.3`.
We should up...You cannot import the example Grafana dashboards to a modern Grafana instance.
![image](/uploads/a95f33a1aa876ae18d92057fd933fc5f/image.png)
The Stork demo uses the `8.3.7` Grafana version. The latest version is `10.3.3`.
We should upgrade the Grafana (and maybe Prometheus) used in the demo and migrate the example dashboards to a modern format.1.16https://gitlab.isc.org/isc-projects/stork/-/issues/1321Enable running Stork on macbook M32024-03-04T19:25:10ZMarcin SiodelskiEnable running Stork on macbook M3There are several things that need to be changed in building Stork (mainly concerning the docker Demo) to run it on macbook with M3 processor. To list the main two: the architecture name "arm64" is not recognized in the rake files. Secon...There are several things that need to be changed in building Stork (mainly concerning the docker Demo) to run it on macbook with M3 processor. To list the main two: the architecture name "arm64" is not recognized in the rake files. Second, we need to emulate arm64 in the docker images becuase of lack of the certain Docker images (flamethrower, bind9 image).1.16Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/1320Duplicated rows in the service table2024-02-28T16:28:53ZSlawek FigielDuplicated rows in the service tableThe problem was reported [on the Stork-users mailing list](https://lists.isc.org/pipermail/stork-users/2024-February/000245.html).
The `service` table rows may be duplicated on some unknown conditions. It causes the HA status displayed ...The problem was reported [on the Stork-users mailing list](https://lists.isc.org/pipermail/stork-users/2024-February/000245.html).
The `service` table rows may be duplicated on some unknown conditions. It causes the HA status displayed on the Dashboard to diverge from the status presented on the application page.
The user reports that the problem occurs in Stork 1.15 but was also observed in the previous versions. The first installed version was 1.12.
Stork was installed long after configuring HA in Kea.
It seems the same problem was reported in #616 and #818.
We should check if the problem were fixed correctly in 1.7 and if the invalid table state may preserved from the previous versions.
We should also analyze if adding the unique constraint on the `service` table would be beneficial to avoid similar issues.1.16Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/1319Package issues during update2024-03-28T13:33:54ZDarren AnkneyPackage issues during updateIt was found that when updating to Stork 1.15.0 (in this case from 1.14.0) on RHEL 7 (and CentOS 7 though engineering states that this problem likely applies to all versions) that there are two problems encountered:
1. The Stork Server ...It was found that when updating to Stork 1.15.0 (in this case from 1.14.0) on RHEL 7 (and CentOS 7 though engineering states that this problem likely applies to all versions) that there are two problems encountered:
1. The Stork Server service ends up stopped in the disabled state even though it was enabled and started prior to update.
2. The `useradd` call in the postinstall script sets the homedir to `/var/lib` instead of `/var/lib/stork-server`.
A patch was provided by the reporter:
```
diff --git a/etc/hooks/rpm/isc-stork-server.postinst b/etc/hooks/rpm/isc-stork-server.postinst
index 3b890b75..7833efd4 100644
--- a/etc/hooks/rpm/isc-stork-server.postinst
+++ b/etc/hooks/rpm/isc-stork-server.postinst
@@ -4,5 +4,5 @@ set -eu
# add stork-server user if does not exist
if ! getent passwd stork-server > /dev/null; then
- useradd --system --home-dir /var/lib/ stork-server
+ useradd --system --base-dir /var/lib/ stork-server
fi
diff --git a/etc/hooks/rpm/isc-stork-server.prerm b/etc/hooks/rpm/isc-stork-server.prerm
index e4649e2c..cc007fbc 100644
--- a/etc/hooks/rpm/isc-stork-server.prerm
+++ b/etc/hooks/rpm/isc-stork-server.prerm
@@ -1,16 +1,17 @@
#!/bin/sh
set -eu
-
-has_active_systemd=0
-if command -v systemctl > /dev/null; then
- status=$(systemctl is-system-running || true)
- if [ "${status}" = "running" ] || [ "${status}" = "degraded" ] || [ "${status}" = "maintenance" ]; then
- has_active_systemd=1
+if [ "$1" -eq 0 ]; then # Uninstall == 0 not Upgrade == 1
+ has_active_systemd=0
+ if command -v systemctl > /dev/null; then
+ status=$(systemctl is-system-running || true)
+ if [ "${status}" = "running" ] || [ "${status}" = "degraded" ] || [ "${status}" = "maintenance" ]; then
+ has_active_systemd=1
+ fi
fi
-fi
-if [ $has_active_systemd -eq 1 ]; then
- systemctl disable isc-stork-server
- systemctl stop isc-stork-server
-fi
+ if [ $has_active_systemd -eq 1 ]; then
+ systemctl disable isc-stork-server
+ systemctl stop isc-stork-server
+ fi
+fi
```
[SF1727](https://isc.lightning.force.com/lightning/r/Case/500S6000005dJugIAE/view)1.16Slawek FigielSlawek Figiel