stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2020-05-14T14:53:52Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/132Go code when run in containers should be built in containers2020-05-14T14:53:52ZMichal NowikowskiGo code when run in containers should be built in containersOtherwise when code is built on e.g. macOS it is not possible to run such binaries in a container with Linux.
Such error is observed:
```
`server_1 | /bin/sh: 1: /server/stork-server: Exec format error`
```Otherwise when code is built on e.g. macOS it is not possible to run such binaries in a container with Linux.
Such error is observed:
```
`server_1 | /bin/sh: 1: /server/stork-server: Exec format error`
```0.8Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/213serverless mode: agent as prometheus exporter2020-05-22T14:35:54ZTomek Mrugalskiserverless mode: agent as prometheus exporterThere are two tickets in Kea (https://gitlab.isc.org/isc-projects/kea/issues/279 and https://gitlab.isc.org/isc-projects/kea/issues/280) that requested having Prometheus exporter and Grafana template. We could address this request using ...There are two tickets in Kea (https://gitlab.isc.org/isc-projects/kea/issues/279 and https://gitlab.isc.org/isc-projects/kea/issues/280) that requested having Prometheus exporter and Grafana template. We could address this request using stork agent. The agent would be working in exporter-only mode.
This should be reasonably simple to implement. There should be a command line switch (or some entry in the config file) that would prevent agent from opening grpc socket and only open Prometheus export socket.
(on a somewhat related note, there should be a way to do the opposite - only open grpc and not open Prometheus socket. That's to address scenario where user is not interested in Grafana).0.8https://gitlab.isc.org/isc-projects/stork/-/issues/218Port bind_exporter to embedded Stork exporter2020-07-10T12:35:19ZMatthijs Mekkingmatthijs@isc.orgPort bind_exporter to embedded Stork exporter0.8Matthijs Mekkingmatthijs@isc.orgMatthijs Mekkingmatthijs@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/issues/245Subnet filtering bug: showing the same subnet several times2020-05-29T14:51:28ZTomek MrugalskiSubnet filtering bug: showing the same subnet several timesThere's a bug in filtering subnets. I have only agent-kea configured. It reports there are 9 subnets. I went to DHCP->Subnets and used "6" as a filtering string hoping to see only 192.0.6.0 subnet. However, it now shows 11 subnets includ...There's a bug in filtering subnets. I have only agent-kea configured. It reports there are 9 subnets. I went to DHCP->Subnets and used "6" as a filtering string hoping to see only 192.0.6.0 subnet. However, it now shows 11 subnets including 3 copies of 192.0.6.0.
If I use a longer filter string 0.6.0 it now limits the subnets correctly, but still shows 3 copies of 192.0.6.0 subnet.
This is what I have in the db:
```
stork=> select * from subnet;
id | created_at | prefix | shared_network_id | client_class | addr_utilization | pd_utilization
----+---------------------------+---------------+-------------------+--------------+------------------+----------------
1 | 2020-04-20 11:35:49.21212 | 192.0.5.0/24 | 1 | class-01-00 | |
2 | 2020-04-20 11:35:49.21212 | 192.0.6.0/24 | 1 | class-01-01 | |
3 | 2020-04-20 11:35:49.21212 | 192.0.7.0/24 | 1 | class-01-02 | |
4 | 2020-04-20 11:35:49.21212 | 192.0.8.0/24 | 1 | class-01-03 | |
5 | 2020-04-20 11:35:49.21212 | 192.0.9.0/24 | 1 | class-01-04 | |
6 | 2020-04-20 11:35:49.21212 | 192.1.15.0/24 | 2 | class-02-00 | |
7 | 2020-04-20 11:35:49.21212 | 192.1.16.0/24 | 2 | class-02-01 | |
8 | 2020-04-20 11:35:49.21212 | 192.1.17.0/24 | 2 | class-02-02 | |
9 | 2020-04-20 11:35:49.21212 | 192.0.2.0/24 | | class-00-00 | |
(9 rows)
```
and this is how it looks filtered:
![bug-duplicate-subnets](/uploads/93df4695f51dd1872cb44ec193bcf405/bug-duplicate-subnets.png)0.8Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/248after entering kea app page with ha status there are lots of errors in the we...2020-06-03T18:16:19ZMichal Nowikowskiafter entering kea app page with ha status there are lots of errors in the web browser consolethe errors:
```
ERROR TypeError: "this._receivedStatus is undefined"
```the errors:
```
ERROR TypeError: "this._receivedStatus is undefined"
```0.8Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/267Enhance search expressions2020-05-29T04:20:30ZMarcin SiodelskiEnhance search expressionsWe currently allow including key=val expressions in search. We think that we might better migrate to something more sophisticated. One particular use case that we already have is to search for all global host reservations. For that we'd ...We currently allow including key=val expressions in search. We think that we might better migrate to something more sophisticated. One particular use case that we already have is to search for all global host reservations. For that we'd like to be able to say:
```
is:global
```
We may also migrate from key=val to key:val.0.8Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/271Sanity checks for 0.7.02022-02-02T09:51:30ZMichal NowikowskiSanity checks for 0.7.01) Please, get the tarball and check it, run tests.
1) tarball: https://gitlab.isc.org/isc-projects/stork/-/jobs/876122/artifacts/browse
1) Start demo locally (rake docker_up) and follow the steps from https://gitlab.isc.org/isc-proje...1) Please, get the tarball and check it, run tests.
1) tarball: https://gitlab.isc.org/isc-projects/stork/-/jobs/876122/artifacts/browse
1) Start demo locally (rake docker_up) and follow the steps from https://gitlab.isc.org/isc-projects/stork/-/wikis/Demo
1) Install server and agent localy e.g. in VMs from binary packages:
1) debs: https://gitlab.isc.org/isc-projects/stork/-/jobs/876123/artifacts/browse
1) rpms: https://gitlab.isc.org/isc-projects/stork/-/jobs/876124/artifacts/browse0.8https://gitlab.isc.org/isc-projects/stork/-/issues/273stork-agent cannot read bind config files that have 600 persmissions2020-05-18T12:54:55ZMichal Nowikowskistork-agent cannot read bind config files that have 600 persmissions@garbled1 reported in #243:
```
This was what told me there was an error:
May 9 06:05:35 pollux stork-agent[28307]: #33 (closed)[33mWARN#033[0m[2020-05-09 06:05:35] bind9.go:254 cannot parse BIND 9 config file /etc/bind/nam...@garbled1 reported in #243:
```
This was what told me there was an error:
May 9 06:05:35 pollux stork-agent[28307]: #33 (closed)[33mWARN#033[0m[2020-05-09 06:05:35] bind9.go:254 cannot parse BIND 9 config file /etc/bind/named.conf: exit status 1
At the top of that file, I include /etc/bind/rndc.key
Easy fix was to edit /etc/group:
bind:x:113:stork-agent
```
stork-agent could be added to bind group during installation if this group exists0.8https://gitlab.isc.org/isc-projects/stork/-/issues/274stork-agent should be able to determine CWD of kea or named processes2022-07-04T07:26:19ZMichal Nowikowskistork-agent should be able to determine CWD of kea or named processes@garbled1 reported in #243:
```
I keep getting this in my logs:
May 11 05:55:10 pollux stork-agent[29532]: #33 (closed)[33mWARN#033[0m[2020-05-11 05:55:10] monitor.go:159 cannot get process current working directory: readlink ...@garbled1 reported in #243:
```
I keep getting this in my logs:
May 11 05:55:10 pollux stork-agent[29532]: #33 (closed)[33mWARN#033[0m[2020-05-11 05:55:10] monitor.go:159 cannot get process current working directory: readlink /proc/22855/cwd: permission denied
lrwxrwxrwx 1 bind bind 0 Apr 18 13:32 /proc/22855/cwd -> /var/cache/bind
drwxr-xr-x 9 root root 4096 Oct 12 2019 /var/cache
drwxrwxr-x 2 root bind 4096 May 11 03:19 /var/cache/bind
That is probably apparmor related?
```
This can be solved by adding:
```
AmbientCapabilities=CAP_SYS_PTRACE
```
to service file.
`CAP_SYS_PTRACE` gives permission to read `/proc/<pid>/cwd`0.8https://gitlab.isc.org/isc-projects/stork/-/issues/275implement refresh data model2020-06-05T16:31:45ZMichal Nowikowskiimplement refresh data modelaccording to this design: https://gitlab.isc.org/isc-projects/stork/-/wikis/Designs/Refreshing-Dataaccording to this design: https://gitlab.isc.org/isc-projects/stork/-/wikis/Designs/Refreshing-Data0.8Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/276Accept new format of the status-get command2020-05-29T05:39:05ZMarcin SiodelskiAccept new format of the status-get commandIn Kea 1.7.8 we are going to have new format of the `status-get` command. See https://gitlab.isc.org/isc-projects/kea/-/issues/1087. Stork should be prepared to accept this new format. In addition to moving the existing parameters there ...In Kea 1.7.8 we are going to have new format of the `status-get` command. See https://gitlab.isc.org/isc-projects/kea/-/issues/1087. Stork should be prepared to accept this new format. In addition to moving the existing parameters there are also new parameters returned which describe the state of the failover when the communication between the servers is interrupted.0.8Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/291Use "Host Reservations" in place of "Hosts and Reservations" - nit2020-06-10T09:09:36ZVicky Riskvicky@isc.orgUse "Host Reservations" in place of "Hosts and Reservations" - nitIt looks like this is going to be a list of servers (hosts) as well as a list of DHCP reservations.
The mouseover explains it is a list of Host Reservations. That should be the title on the page, (unless we are planning to add a bunch o...It looks like this is going to be a list of servers (hosts) as well as a list of DHCP reservations.
The mouseover explains it is a list of Host Reservations. That should be the title on the page, (unless we are planning to add a bunch of additional information on the hosts themselves at some later point?)
If it fits, it would be good if that was also the link in the top nav (Host Reservations) so that we are consistent.
![Screen_Shot_2020-05-26_at_11.58.23_AM](/uploads/43d9dd25def940789011ac8c9150839f/Screen_Shot_2020-05-26_at_11.58.23_AM.png)0.8https://gitlab.isc.org/isc-projects/stork/-/issues/302Docker based demo should use Kea 1.7.82020-05-29T13:16:13ZMarcin SiodelskiDocker based demo should use Kea 1.7.8Our demo setup uses Kea 1.7.4 and Kea 1.7.3 for various agents being installed on docker containers. Kea 1.7.8 introduces new information about HA setup returned in response to the status-get command. To see this information we'd need to...Our demo setup uses Kea 1.7.4 and Kea 1.7.3 for various agents being installed on docker containers. Kea 1.7.8 introduces new information about HA setup returned in response to the status-get command. To see this information we'd need to upgrade our containers (at least ha1 and ha2) to use Kea 1.7.8.0.8https://gitlab.isc.org/isc-projects/stork/-/issues/303Host reservations need to include hostname and PXE boot params2020-06-02T11:46:22ZMarcin SiodelskiHost reservations need to include hostname and PXE boot paramsThe following requirement asks for displaying additional information together with the IP host reservations: https://gitlab.isc.org/isc-projects/stork/-/issues/45.
This should be fetched from Kea servers and stored in the database, so a...The following requirement asks for displaying additional information together with the IP host reservations: https://gitlab.isc.org/isc-projects/stork/-/issues/45.
This should be fetched from Kea servers and stored in the database, so as it can be displayed.0.8Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/304Specify the Kea version # required to enable Stork features in the Stork ARM2020-06-15T13:54:24ZVicky Riskvicky@isc.orgSpecify the Kea version # required to enable Stork features in the Stork ARMIn the arm it says
'Stork Server and Stork Agent have been tested thoroughly on the Ubuntu 18.04 system. They have been tested and run on the Fedora 31 system as well.
The Stork Agent does not require any specific dependencies to run. I...In the arm it says
'Stork Server and Stork Agent have been tested thoroughly on the Ubuntu 18.04 system. They have been tested and run on the Fedora 31 system as well.
The Stork Agent does not require any specific dependencies to run. It can be run immediately after installation.'
This isn't really true. For Stork to work, you need some minimum Kea version. Then some other Stork features depend on having specific Kea hook modules loaded. IW need some explicit dependencies on Kea (and BIND) versions here.0.8https://gitlab.isc.org/isc-projects/stork/-/issues/308Show last failover time in the dashboard2020-06-05T09:05:46ZMarcin SiodelskiShow last failover time in the dashboardThis ticket is meant to address two requirements listed in the #216:
- Show last failover time
- Clicking on the HA status should navigate to the details of the HA statusThis ticket is meant to address two requirements listed in the #216:
- Show last failover time
- Clicking on the HA status should navigate to the details of the HA status0.8Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/316agent crashes when it encounters unknown stat from kea2020-06-10T12:35:15ZMichal Nowikowskiagent crashes when it encounters unknown stat from keahttps://support.isc.org/Ticket/Display.html?id=16582https://support.isc.org/Ticket/Display.html?id=165820.8Michal NowikowskiMichal Nowikowski