stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2020-07-09T15:26:51Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/329Enable authentication for the traffic generators2020-07-09T15:26:51ZMarcin SiodelskiEnable authentication for the traffic generatorsNow that we have fixed a bug that allowed for unauthorized access to some Stork views we need to modify the DHCP and DNS traffic generators to create the session (login) prior to getting configured DHCP subnets from the server. Without t...Now that we have fixed a bug that allowed for unauthorized access to some Stork views we need to modify the DHCP and DNS traffic generators to create the session (login) prior to getting configured DHCP subnets from the server. Without this, the traffic generators fail t get the list of subnets and this makes them unusable.
The useful reference I got from @godfryd was: https://requests.readthedocs.io/en/master/user/advanced/0.9Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/320adapt deploy_demo in .gitlab-ci.yml to new model of building demo (docker_up)2020-06-16T13:22:15ZMichal Nowikowskiadapt deploy_demo in .gitlab-ci.yml to new model of building demo (docker_up)0.9Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/485agent-server TLS part 4: adapt Stork demo to new machine registration methods2021-03-02T07:38:51ZMarcin Siodelskiagent-server TLS part 4: adapt Stork demo to new machine registration methodsAfter implementing #483 it is necessary to modify docker configuration and apply other changes to be able to run the demo with the new agent registration methods.After implementing #483 it is necessary to modify docker configuration and apply other changes to be able to run the demo with the new agent registration methods.0.15Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/522demo deployment fails2021-04-07T05:25:19ZMichal Nowikowskidemo deployment failsit fails due to docker compose yaml files version mismatch:
```
Version mismatch: file ./deploy/docker-compose.yaml specifies version 2.1 but extension file ./deploy/docker-compose-premium.yaml uses version 3.0
```it fails due to docker compose yaml files version mismatch:
```
Version mismatch: file ./deploy/docker-compose.yaml specifies version 2.1 but extension file ./deploy/docker-compose-premium.yaml uses version 3.0
```0.16Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/517Connectivity issues between the server and agent-kea in Stork demo2021-03-29T09:22:54ZMarcin SiodelskiConnectivity issues between the server and agent-kea in Stork demoI observed an issue whereby I authorize the "agent-kea" machine in our Docker demo but Stork server apparently can't communicate with the agent reporting "Cannot get machine state".
The issue appears to be related to the fact that agent...I observed an issue whereby I authorize the "agent-kea" machine in our Docker demo but Stork server apparently can't communicate with the agent reporting "Cannot get machine state".
The issue appears to be related to the fact that agent-kea is connected to several Docker networks. Its /etc/hosts file maps agent-kea hostname to multiple IP addresses and depending on which address is first in the /etc/hosts, the name agent-kea may resolve to a wrong one. As a result the agent binds to a wrong address and server can't communicate with it.0.16https://gitlab.isc.org/isc-projects/stork/-/issues/494Broken prometheus-node-exporter on agent-kea-ha2 in demo2021-03-11T14:45:55ZTomek MrugalskiBroken prometheus-node-exporter on agent-kea-ha2 in demoThe following discussion from !272 should be addressed:
- [ ] @tomek started a [discussion](https://gitlab.isc.org/isc-projects/stork/-/merge_requests/272#note_196658):
> I've noticed there's prometheus-node-exporter not running o...The following discussion from !272 should be addressed:
- [ ] @tomek started a [discussion](https://gitlab.isc.org/isc-projects/stork/-/merge_requests/272#note_196658):
> I've noticed there's prometheus-node-exporter not running on kea-ha2. Not sure if it's related to the demo changes or not. In any case, that's something that can easily be kicked to a separate ticket.
>
> ![ha2-services](/uploads/7ddb5886c5ce4a16c10988d6c4ce41a9/ha2-services.png)0.16Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/542add kea with mysql or posgresql to demo2021-05-24T10:24:07ZMichal Nowikowskiadd kea with mysql or posgresql to demoThis would allow showing in UI that reservations are stored in DB.This would allow showing in UI that reservations are stored in DB.0.18Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/566cleanup Rakefile and .gitlab-ci.yml2021-08-04T15:32:13ZMichal Nowikowskicleanup Rakefile and .gitlab-ci.ymlThe code has been moved from .gitlab-ci.yml to Rakefile and formed new task: build_and_push_demo_images.
Now there are 2 symetric and similar tasks: `docker_up` and `build_and_push_demo_images`.
They both use common `build_all_in_contain...The code has been moved from .gitlab-ci.yml to Rakefile and formed new task: build_and_push_demo_images.
Now there are 2 symetric and similar tasks: `docker_up` and `build_and_push_demo_images`.
They both use common `build_all_in_container` task.0.19https://gitlab.isc.org/isc-projects/stork/-/issues/565harden demo deployment2021-08-02T13:57:35ZMichal Nowikowskiharden demo deployment0.19Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/445Crashes observed in traffic simulator in 0.132022-02-04T09:06:46ZMarcin SiodelskiCrashes observed in traffic simulator in 0.13This is a result of sanity checks for 0.13.0. See the following comment: https://gitlab.isc.org/isc-projects/stork/-/issues/441#note_174569
It was pointed out that:
"After using Stork Demo for a while I wanted to try Stork Environment ...This is a result of sanity checks for 0.13.0. See the following comment: https://gitlab.isc.org/isc-projects/stork/-/issues/441#note_174569
It was pointed out that:
"After using Stork Demo for a while I wanted to try Stork Environment Simulator. I noticed that it crashes on http://localhost:5000/services URL."
With the following stack trace:
```
Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 2464, in __call__
return self.wsgi_app(environ, start_response)
File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 2450, in wsgi_app
response = self.handle_exception(e)
File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1867, in handle_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python3.6/dist-packages/flask/_compat.py", line 39, in reraise
raise value
File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 2447, in wsgi_app
response = self.full_dispatch_request()
File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1952, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1821, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python3.6/dist-packages/flask/_compat.py", line 39, in reraise
raise value
File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1950, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python3.6/dist-packages/flask/app.py", line 1936, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/sim/sim.py", line 309, in get_services
data = _get_services()
File "/sim/sim.py", line 284, in _get_services
machines = r.json()['items']
KeyError: 'items'
```1.0-backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/615access denied in deploy_demo2021-12-02T13:17:20ZAndrei Pavelandrei@isc.orgaccess denied in deploy_demohttps://stork.lab.isc.org/ has been offline for a while because of the following error in `deploy_demo`:
https://gitlab.isc.org/isc-projects/stork/-/jobs/2095564
```
Pushing agent-kea-premium (registry.gitlab.isc.org/isc-private/stork/...https://stork.lab.isc.org/ has been offline for a while because of the following error in `deploy_demo`:
https://gitlab.isc.org/isc-projects/stork/-/jobs/2095564
```
Pushing agent-kea-premium (registry.gitlab.isc.org/isc-private/stork/agent-kea-premium:latest)...
The push refers to repository [registry.gitlab.isc.org/isc-private/stork/agent-kea-premium]
denied: requested access to the resource is denied
rake aborted!
Command failed with status (1): [docker-compose -f docker-compose.yaml -f d...]
/builds/isc-projects/stork/Rakefile:672:in `block in <top (required)>'
Tasks: TOP => build_and_push_demo_images
```1.0https://gitlab.isc.org/isc-projects/stork/-/issues/686deploy_demo deploys old version of stork2022-02-02T13:58:59ZAndrei Pavelandrei@isc.orgdeploy_demo deploys old version of storkOn release of 1.1.0, the login page displayed version 1.0.0, showing a problem with what version is being deployed in the demo.On release of 1.1.0, the login page displayed version 1.0.0, showing a problem with what version is being deployed in the demo.1.1Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/issues/604DHCP6 simulator seems not working2022-01-27T18:22:04ZSlawek FigielDHCP6 simulator seems not workingI cannot simulate any DHCPv6 traffic. It looks like a problem with the simulator itself because the `kea_dhcp6_addresses_declined_total` metric has a value equal to 1 when I'm starting the traffic generator.I cannot simulate any DHCPv6 traffic. It looks like a problem with the simulator itself because the `kea_dhcp6_addresses_declined_total` metric has a value equal to 1 when I'm starting the traffic generator.1.1Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/761Guide to run the demo quickly2022-07-14T07:23:26ZSlawek FigielGuide to run the demo quicklyIt is feedback after the demo presentation from Greg:
We need a guide or script to run the demo without a rake, or we should prepare the step-by-step instruction on how to install all requirements.It is feedback after the demo presentation from Greg:
We need a guide or script to run the demo without a rake, or we should prepare the step-by-step instruction on how to install all requirements.1.5Slawek FigielSlawek Figielhttps://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/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 Figielhttps://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/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/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/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 Becheriu