stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2024-03-26T14:53:23Zhttps://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/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/1289Fix metrics endpoint in demo2024-03-05T10:31:36ZSlawek FigielFix metrics endpoint in demoThe server's `/metrics` endpoint is unavailable in the demo environment due to the misconfiguration of Nginx.
This issue contains the changes made during the analysis of #1214.The server's `/metrics` endpoint is unavailable in the demo environment due to the misconfiguration of Nginx.
This issue contains the changes made during the analysis of #1214.1.16Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1259Stork webinar preparation2024-01-02T12:31:56ZMarcin SiodelskiStork webinar preparationIn order to run the Stork webinar on Dec 13, 2023 we need need some small demo updates and fixes.In order to run the Stork webinar on Dec 13, 2023 we need need some small demo updates and fixes.1.15Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/1257Simulator is not working due to incompatible dependency2023-12-08T16:31:05ZSlawek FigielSimulator is not working due to incompatible dependencyThe `isc-kea-common` package is not explicitly set in the `simulator.Dockerfile`.
It causes the incompatible version of this package to be installed after the recent Kea update.
```
root@simulator:/app# perfdhcp
perfdhcp: error while l...The `isc-kea-common` package is not explicitly set in the `simulator.Dockerfile`.
It causes the incompatible version of this package to be installed after the recent Kea update.
```
root@simulator:/app# perfdhcp
perfdhcp: error while loading shared libraries: libkea-dhcp++.so.73: cannot open shared object file: No such file or directory
```Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1236stork-demo.sh is failing to build the web ui for stork2023-12-07T16:49:30Zvarsrajastork-demo.sh is failing to build the web ui for stork---
name: Bug report
about: store-demo.sh fails to build the web ui for stork
---
**Describe the bug**
Trying to build the stork server, web-ui web-apache docker containers . Checked out the latest code and tried to run the stork-dem...---
name: Bug report
about: store-demo.sh fails to build the web ui for stork
---
**Describe the bug**
Trying to build the stork server, web-ui web-apache docker containers . Checked out the latest code and tried to run the stork-demo.sh script that builds these images. it is exiting with error to build the web-ui image.
**Expected behavior**
Able to see the stork demo to start running.
[stork-demo-error.txt](/uploads/d0b03d0046b4202bd0a5c440896b549a/stork-demo-error.txt)
**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.https://gitlab.isc.org/isc-projects/stork/-/issues/1192Starting fresh demo fails for modern docker compose2024-02-13T14:22:35ZSlawek FigielStarting fresh demo fails for modern docker composeThe issue was found during [1.13 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1187#note_408649) by @slawek.
`rake demo:up` fails:
```
deep@deep:~/Downloads/artifacts (62)/stork-1.13.0$ rake demo:up CS_REPO_ACCESS_T...The issue was found during [1.13 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1187#note_408649) by @slawek.
`rake demo:up` fails:
```
deep@deep:~/Downloads/artifacts (62)/stork-1.13.0$ rake demo:up CS_REPO_ACCESS_TOKEN=...
docker compose --project-directory . -f docker/docker-compose.yaml -f docker/docker-compose-premium.yaml build
[+] Building 1.9s (8/8) FINISHED docker-container:stork
=> CANCELED [server internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [agent-kea internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [agent-kea6 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [agent-kea-ha2 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [agent-bind9-2 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
=> CANCELED [kea-config-generator internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.7s
=> => creating container buildx_buildkit_stork0 0.2s
=> ERROR [agent-bind9 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.8s
=> => creating container buildx_buildkit_stork0 0.1s
=> CANCELED [agent-kea-ha1 internal] booting buildkit 1.9s
=> => pulling image moby/buildkit:buildx-stable-1 1.9s
------
> [agent-bind9 internal] booting buildkit:
------
Error response from daemon: Conflict. The container name "/buildx_buildkit_stork0" is already in use by container "aad862ed4f9cc3c211de2308c3475379f7f5e2835d646f4a7e5f78186e717d0a". You have to remove (or rename) that container to be able to reuse that name.
rake aborted!
Command failed with status (17): [docker compose --project-directory . -f do...]
/home/deep/Downloads/artifacts (62)/stork-1.13.0/rakelib/60_docker_demo.rake:98:in `docker_up_services'
/home/deep/Downloads/artifacts (62)/stork-1.13.0/rakelib/60_docker_demo.rake:116:in `block (2 levels) in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
Tasks: TOP => demo:up
(See full trace by running task with --trace)
```
My setup:
```
$ docker version
Client:
Version: 24.0.5
API version: 1.41 (downgraded from 1.43)
Go version: go1.20.3
Git commit: 24.0.5-0ubuntu1~22.04.1
Built: Mon Aug 21 19:50:14 2023
OS/Arch: linux/amd64
Context: default
Server:
Engine:
Version: 20.10.24
API version: 1.41 (minimum version 1.12)
Go version: go1.20.7
Git commit: 5d6db84
Built: Wed Aug 23 20:55:00 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.6.20
GitCommit: 2806fc1057397dbaeefbea0e4e17bddfbd388f38
runc:
Version: 1.1.5
GitCommit:
docker-init:
Version: 0.19.0
GitCommit: de40ad0
```
```
$ docker compose version
Docker Compose version v2.21.0
```
```
$ docker buildx version
github.com/docker/buildx v0.11.2 9872040
```
Workaround: Call `rake demo:build` and next `rake demo:up`
The same problem is described [on StackOverflow](https://stackoverflow.com/questions/76275277/docker-compose-cache-from-cache-to-buildx-the-container-name-buildx-buildk).outstandinghttps://gitlab.isc.org/isc-projects/stork/-/issues/1181Hooks in system tests2024-02-06T14:41:53ZSlawek FigielHooks in system testsThere should be a possibility to write the system tests for hooks and use hook in demo.There should be a possibility to write the system tests for hooks and use hook in demo.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1156Demo: agent-kea6 doesn't work2023-09-15T11:18:22ZSlawek FigielDemo: agent-kea6 doesn't workThere is an observed issue:
```
ERROR DHCP6_PARSER_FAIL failed to create or run parser for configuration element shared-networks: Failed to create pool defined by: 4001:db8:1:0:abcd::/64 (/etc/kea/kea-dhcp6.conf:390:42) (/etc/kea/kea-dh...There is an observed issue:
```
ERROR DHCP6_PARSER_FAIL failed to create or run parser for configuration element shared-networks: Failed to create pool defined by: 4001:db8:1:0:abcd::/64 (/etc/kea/kea-dhcp6.conf:390:42) (/etc/kea/kea-dhcp6.conf:383:9)
ERROR DHCP6_CONFIG_LOAD_FAIL configuration error using file: /etc/kea/kea-dhcp6.conf, reason: Failed to create pool defined by: 4001:db8:1:0:abcd::/64 (/etc/kea/kea-dhcp6.conf:390:42) (/etc/kea/kea-dhcp6.conf:383:9)
2023-09-07 11:21:27.539 ERROR [kea-dhcp6.dhcp6/109.140467203000768] DHCP6_INIT_FAIL failed to initialize Kea server: configuration error using file '/etc/kea/kea-dhcp6.conf': Failed to create pool defined by: 4001:db8:1:0:abcd::/64 (/etc/kea/kea-dhcp6.conf:390:42) (/etc/kea/kea-dhcp6.conf:383:9)
2023-09-07 11:21:27,540 INFO exited: kea-dhcp6 (exit status 1; not expected)
```1.13Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1054Simulator doesn't work2023-06-16T05:46:26ZSlawek FigielSimulator doesn't workThe issues were found by @slawek [during 1.11 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1048#note_379526).
The simulator doesn't work. It uses the out-of-data request structure to create a session so the server r...The issues were found by @slawek [during 1.11 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1048#note_379526).
The simulator doesn't work. It uses the out-of-data request structure to create a session so the server rejects its connections.1.12Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/1013Configure Kea Control Agent with TLS in demo2023-05-30T13:39:16ZSlawek FigielConfigure Kea Control Agent with TLS in demoThe issue was reported by @slawek during 1.10 sanity checks. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/1009#note_364515).
At least one Kea Control Agent in the demo should be configured to accept only TLS connections.The issue was reported by @slawek during 1.10 sanity checks. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/1009#note_364515).
At least one Kea Control Agent in the demo should be configured to accept only TLS connections.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1002Run demo on RHEL92023-03-07T14:32:28ZTomek MrugalskiRun demo on RHEL9@cstrotm reported building demo on RHEL9 was really painful. We should:
- [ ] build the demo on fresh RHEL9
- [ ] update outdated dependencies (outdated docker-compose was mentioned, but there may be others)
- [ ] come up with a proposa...@cstrotm reported building demo on RHEL9 was really painful. We should:
- [ ] build the demo on fresh RHEL9
- [ ] update outdated dependencies (outdated docker-compose was mentioned, but there may be others)
- [ ] come up with a proposal how to run tests on RHEL9 (this may end up in a separate ticket)backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/995Upgrade Kea version in demo and fix systemtests version parsing2023-08-31T17:50:40ZSlawek FigielUpgrade Kea version in demo and fix systemtests version parsingThe default Kea version used in the demo (2.0.2) is pretty old; we should upgrade it.
We should also add some containers with different Kea versions. It's possible from a few releases by providing build arguments in compose file.The default Kea version used in the demo (2.0.2) is pretty old; we should upgrade it.
We should also add some containers with different Kea versions. It's possible from a few releases by providing build arguments in compose file.1.13Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/stork/-/issues/979Stork Demo uses deprecated "docker-compose" command2023-03-29T18:11:00ZCarsten StrotmannStork Demo uses deprecated "docker-compose" commandThe Stork Demo rake target uses the "docker-compose" command, which is written in Python and (according to https://docs.docker.com/compose/release-notes/) deprecated and will not be supported after summer 2023. It is already hard to inst...The Stork Demo rake target uses the "docker-compose" command, which is written in Python and (according to https://docs.docker.com/compose/release-notes/) deprecated and will not be supported after summer 2023. It is already hard to install on recent Linux systems, such as Red Hat EL 9.
The rake target should migrate to the new "docker compose" command (docker-compose V2).1.10Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/932stork-install-agent.sh missing2024-03-27T10:50:22ZLarry G. Wapnitskystork-install-agent.sh missingJust installed stork server, and am unable to get the agent installed using the script:
```
# wget http://10.150.33.4:8080/stork-install-agent.sh
--2023-01-04 16:59:54-- http://10.150.33.4:8080/stork-install-agent.sh
Connecting to 10.1...Just installed stork server, and am unable to get the agent installed using the script:
```
# wget http://10.150.33.4:8080/stork-install-agent.sh
--2023-01-04 16:59:54-- http://10.150.33.4:8080/stork-install-agent.sh
Connecting to 10.150.33.4:8080... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2023-01-04 16:59:54 ERROR 500: Internal Server Error.
```backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/923Docker container with both Kea and BIND 92022-12-13T14:56:51ZSlawek FigielDocker container with both Kea and BIND 9We use the Kea and BIND 9 containers in demo and system tests. Currently, these applications are available in separate containers with the Stork Agent installed. We can't run a single container with both Kea and BIND 9. it makes some pro...We use the Kea and BIND 9 containers in demo and system tests. Currently, these applications are available in separate containers with the Stork Agent installed. We can't run a single container with both Kea and BIND 9. it makes some problems impossible to detect, as #900 shows.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/824stork-demo.sh doesn't work on macOS2022-08-17T15:06:56ZMarcin Siodelskistork-demo.sh doesn't work on macOSI get the following error on macOS when I try to run `stork-demo.sh`:
```
./stork-demo.sh -h
getopt: illegal option -- n
```I get the following error on macOS when I try to run `stork-demo.sh`:
```
./stork-demo.sh -h
getopt: illegal option -- n
```1.6Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/820Unify the Nginx configurations.2022-08-09T13:41:14ZSlawek FigielUnify the Nginx configurations.We have two different Nginx configuration files in the Stork repository:
- `etc/Nginx-stork.conf`
- `webui/nginx.conf`
Our documentation recommends the first file, but the second one is used to deploy the Stork demo.
We don't check if ...We have two different Nginx configuration files in the Stork repository:
- `etc/Nginx-stork.conf`
- `webui/nginx.conf`
Our documentation recommends the first file, but the second one is used to deploy the Stork demo.
We don't check if the first config is valid.
We should have only one Nginx configuration that will be recommended example and used in the demo.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/811Limit maintenance downtime during deploying the demo2022-10-25T13:33:56ZSlawek FigielLimit maintenance downtime during deploying the demoCurrently, to deploy a demo, we first shut down an old version, and next, we build and run a new one. The build takes ~1 hour. The demo is not available at this time. We can refactor our solution to build the demo in the first order and ...Currently, to deploy a demo, we first shut down an old version, and next, we build and run a new one. The build takes ~1 hour. The demo is not available at this time. We can refactor our solution to build the demo in the first order and restart it next. It should significantly limit maintenance downtime.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/810Deploy demo doesn't work2022-08-17T15:06:56ZSlawek FigielDeploy demo doesn't workWe changed the name of the running demo script in #761, but we forgot to update the Gitlab CI YAML. The deploy demo CI tasks fail now due to a missing file.We changed the name of the running demo script in #761, but we forgot to update the Gitlab CI YAML. The deploy demo CI tasks fail now due to a missing file.1.6Slawek FigielSlawek Figiel