stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2024-02-27T09:52:35Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/1313Incorrect default *.env file.2024-02-27T09:52:35ZAndreas JentschIncorrect default *.env file.---
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**
If you start the agent with the following command, this output is generated.
/usr/bin/stork-agent --use-env-file
FATA[2024-02-08 10:39:55] main.go:406 invalid environment file: '/etc/stork/server.env': ...
**To Reproduce**
Steps to reproduce the behavior:
1. /usr/bin/stork-agent --env-file '/etc/stork/agent.env' --use-env-file
**Expected behavior**
You should adjust the default value for the .*env file.
**Environment:**
/usr/bin/stork-agent -v
1.15.0
Static hostname: dhcp-01-xgs.glattnet.ch
Icon name: computer-server
Chassis: server 🖳
Machine ID: cf6ef911a0974dbfa031e35e8f775125
Boot ID: 96edd982af2d4745a030003205e7fae2
Operating System: Rocky Linux 9.3 (Blue Onyx)
CPE OS Name: cpe:/o:rocky:rocky:9::baseos
Kernel: Linux 5.14.0-362.18.1.el9_3.x86_64
Architecture: x86-64
Hardware Vendor: HPE
Hardware Model: ProLiant DL360 Gen10
Firmware Version: U32
- Kea version: 2.2.0
tarball
linked with:
log4cplus 2.0.5
OpenSSL 3.0.7 1 Nov 2022
database:
MySQL backend 14.0, library 3.2.6
PostgreSQL backend 13.0, library 130013
Memfile backend 2.1
- Stork: 1.15.0
- OS: Rocky Linux 9.3 (Blue Onyx)
- Kea: Which features were compiled in (in particular which backends)
- Kea: If/which hooks where loaded in
**Contacting you**
E-Mail1.16https://gitlab.isc.org/isc-projects/stork/-/issues/832Feature Request: Documentation not clear about the syntax2022-10-13T10:32:28ZmikygeeFeature Request: Documentation not clear about the syntaxHello,
The documentation
https://stork.readthedocs.io/en/latest/install.html#setup
is not clear about syntax to use netween the parameter and the value
"STORK_REST_HOST - the IP address on which the server listen"
I know by having rea...Hello,
The documentation
https://stork.readthedocs.io/en/latest/install.html#setup
is not clear about syntax to use netween the parameter and the value
"STORK_REST_HOST - the IP address on which the server listen"
I know by having read the issues and mailing list that an equal sign should separate the parameter STORK_REST_HOST and the value defined by an IP
STORK_REST_HOST=1.1.1.1
But when I first read the documentation I was wondering if it should be an equal sign, a colon, something else...
Same for
https://stork.readthedocs.io/en/latest/install.html#agent-configuration-settings
Sometimes configuration lines end with a semi colon, here we don't know if it's the case or not.
Regardsbackloghttps://gitlab.isc.org/isc-projects/stork/-/issues/338Terminology cleanup (services)2024-03-26T11:25:44ZTomek MrugalskiTerminology cleanup (services)One of the conclusions of the UI discussions (see [stork ui](https://pad.isc.org/p/stork-ui)) was that the services naming is confusing. This ticket should cover 2 things:
- [ ] Propose naming update, have a discussion with everyone int...One of the conclusions of the UI discussions (see [stork ui](https://pad.isc.org/p/stork-ui)) was that the services naming is confusing. This ticket should cover 2 things:
- [ ] Propose naming update, have a discussion with everyone interested
- [ ] Once there's general consensus, implement the changes
Couple ideas: rename services to something more intuitive, maybe add a vocabulary, restructure the services view. Some ideas are more expensive to implement than others.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1167Stop asking about server access token when registering a client in an automat...2023-10-17T13:24:29ZPeter MagnussonStop asking about server access token when registering a client in an automated manner---
name: Feature request
about: Stop asking about server access token when registering a client in an automated manner
When automating the registration of a stork agent it still asks for
`>>>> Server access token (optional):` if I pro...---
name: Feature request
about: Stop asking about server access token when registering a client in an automated manner
When automating the registration of a stork agent it still asks for
`>>>> Server access token (optional):` if I provide all other arguments.
It's really helpful when you are in some kind of interactive session
but it creates some mess if you want to automate it with a script.outstandinghttps://gitlab.isc.org/isc-projects/stork/-/issues/563Issue with stork auto discovery2021-09-14T16:00:07ZRishab MehtaIssue with stork auto discoveryHi Team,
I have 2 Ubuntu VMs
1st running stork-server and the postgre required. This is fine and I have he UI up and running.
2nd VM has Kea DHCP installed, configured and running. It also has the stork-agent running (installed from the...Hi Team,
I have 2 Ubuntu VMs
1st running stork-server and the postgre required. This is fine and I have he UI up and running.
2nd VM has Kea DHCP installed, configured and running. It also has the stork-agent running (installed from the stork-server UI).
The 2nd VMs stats are visible and updating on Stork UI, but Kea service isn't auto discovered. Am i missing something?
Rishaboutstanding