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/739Demo: Busy exposed ports disturb the demo2022-05-17T13:36:48ZSlawek FigielDemo: Busy exposed ports disturb the demoThe issue was found during 1.3 sanity checks. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/732#note_285141)
I've been testing on 733aaea2cf70106719d8065de41eeacaec66c126 (master as of today). I like the new build system a...The issue was found during 1.3 sanity checks. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/732#note_285141)
I've been testing on 733aaea2cf70106719d8065de41eeacaec66c126 (master as of today). I like the new build system a lot. The elapsed build time is super useful, as is the general cleaning of the `rake` tasks. I had some problems: forgot to kill prometheus running on my host.
It seems that the docker-compose service fails silently if any exposed port is busy.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/737Demo: Server starts earlier then the database2022-05-17T13:32:45ZSlawek FigielDemo: Server starts earlier then the databaseThe issue was found during 1.3 sanity checks. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/732#note_285141)
I've been testing on 733aaea2cf70106719d8065de41eeacaec66c126 (master as of today). I like the new build system a...The issue was found during 1.3 sanity checks. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/732#note_285141)
I've been testing on 733aaea2cf70106719d8065de41eeacaec66c126 (master as of today). I like the new build system a lot. The elapsed build time is super useful, as is the general cleaning of the `rake` tasks. I had some problems: Something that looked like a race condition (`server_1 | FATA[2022-05-09 14:56:57] main.go:45 cannot start the Stork Server: FATAL #57P03 the database system is starting up`), but after the second attempt it worked well.backloghttps://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/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/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/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/750Stork Server in Demo doesn't contain packages2023-10-16T09:05:41ZSlawek FigielStork Server in Demo doesn't contain packagesOriginally written by @rgomez-eng in #736:
> We also did try to download the agent from the Stork webui of course but we get an error about problem reading `Problem reading 'webui/dist/stork/assets/pkgs' directory with packages: open we...Originally written by @rgomez-eng in #736:
> We also did try to download the agent from the Stork webui of course but we get an error about problem reading `Problem reading 'webui/dist/stork/assets/pkgs' directory with packages: open webui/dist/stork/assets/pkgs: no such file or directory`, which is weird since this image is freshly built from the `server-webui` stage in the provided Dockerfile.
The Stork in the Demo should be fully configured and operational. Currently, it doesn't contain DEB and RPM files. It's possible to include the packages after merging #709.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/738Demo: Auto cleanup deprecated demo2023-10-09T13:51:38ZSlawek FigielDemo: Auto cleanup deprecated demoThe issue was found during 1.3 sanity checks. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/732#note_285141)
I've been testing on 733aaea2cf70106719d8065de41eeacaec66c126 (master as of today). I like the new build system a...The issue was found during 1.3 sanity checks. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/732#note_285141)
I've been testing on 733aaea2cf70106719d8065de41eeacaec66c126 (master as of today). I like the new build system a lot. The elapsed build time is super useful, as is the general cleaning of the `rake` tasks.
I had some problems: some legacy images, running containers, and networks that disturbed the demo to startbacklogTomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/491Consider having at least one machine unregistered in the demo2022-11-16T11:54:50ZMarcin SiodelskiConsider having at least one machine unregistered in the demoCurrently, all agents in the demo setup use agent token based registration to connect with the server. When you start the demo, all of the agents are awaiting authorization. In the review of #483, @tomek suggested that at least one demo ...Currently, all agents in the demo setup use agent token based registration to connect with the server. When you start the demo, all of the agents are awaiting authorization. In the review of #483, @tomek suggested that at least one demo agent should be registrable using the command line. The following is the original comment:
https://gitlab.isc.org/isc-projects/stork/-/merge_requests/272#note_196567backloghttps://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).outstanding