stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2024-03-27T16:57:15Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/1348Remove stork-repo tag from .gitlab-ci.yaml2024-03-27T16:57:15ZSlawek FigielRemove stork-repo tag from .gitlab-ci.yamlThe `upload_to_repo` CI task is not working as described [on MM QA channel](https://mattermost.isc.org/isc/pl/eoq3yfamnbfz7n6tfaewdmc6mh).
We got this error:
> This job is stuck because of one of the following problems. There are no ac...The `upload_to_repo` CI task is not working as described [on MM QA channel](https://mattermost.isc.org/isc/pl/eoq3yfamnbfz7n6tfaewdmc6mh).
We got this error:
> This job is stuck because of one of the following problems. There are no active runners online, no runners for the protected branch, or no
runners that match all of the job's tags:
Its tags defined in the .gitlab-ci.yml file are:
- linux
- aws
- runner-manager
- amd64
- stork-repo
I checked the Stork repository settings and it seems there is no runner that matches the requirements.
The `aws` tag is missing in all runners that have the stork-repo tag.
### Proposed solution:
* remove `stork-repo` tag from `upload_to_repo` job in .gitlab-ci.yml.
* remove `-4` (which enforces IPv4 connection) from `ssh-keyscan -4 repo.isc.org >> ~/.ssh/known_hosts`https://gitlab.isc.org/isc-projects/stork/-/issues/1199Cloudsmith Debian packages (Possibly others) missing assets2023-10-17T13:54:37ZTroy TelfordCloudsmith Debian packages (Possibly others) missing assets---
name: Missing Files in Debian Packages
about: isc-stork-server
---
`isc-stork-server 1.13.0.231011103556`
**Describe the bug** Files aren't being packaged in the Debian (.deb) packages which are being referenced in the program.
**...---
name: Missing Files in Debian Packages
about: isc-stork-server
---
`isc-stork-server 1.13.0.231011103556`
**Describe the bug** Files aren't being packaged in the Debian (.deb) packages which are being referenced in the program.
**To Reproduce** Steps to reproduce the behavior:
1. Install Stork via Debian Packagess
1. I used `isc-stork-server 1.13.0.231011103556` on Debian (Sid) x86-64
2. Login to Stork
3. Click on _Services_ → _Machines_
4. Click on "_How to Install Agent on New Machine_"
5. Read (and follow) the directions in the dialog.
**Expected behavior** Directions should work - specifically:
`wget http://<host>/``stork-install-agent.sh` should download the file.
**Environment:**
- Kea: `2.2.1-3`
- BIND9 version: `1:9.19.17-1`
- Stork: `1.13.0.231011103556`
- OS: Debian `sid` x86_64
- Kea: (Debian Package :shrug:)
- Kea: Haven't gotten that far yet
**Additional Information**: I doubt logs are relevant, but when visiting with a browser, I do see this error message:
`Problem reading '/usr/share/stork/www/assets/pkgs' directory with packages: open /usr/share/stork/www/assets/pkgs: no such file or directory`
**Some initial questions**
- Are you sure your feature is not already implemented in the latest Kea version?
* N/A
- Are you sure what you would like to do is not possible using some other mechanisms?
* There are myriad ways to do it, but I'm pretty sure having the assets included in the Debian package is probably the optimal solution.
- Have you discussed your idea on kea-users or kea-dev mailing lists?
* Not yet.
**Is your feature request related to a problem? Please describe.** Not really a feature, but a bug.
**Describe the solution you'd like** I think this is simply a case of a missing file from the `.deb` package.
**Describe alternatives you've considered**
* Simply downloading from `gitlab` and installing it manually.
* Great for me, but probably not ideal going forward.
* Fixing the Debian package myself
* I've professionally managed RPM packages; I've tried to figure out Debian packages, but have generally been found a short time later muttering Lovecraftian madness. There's always some other undocumented `dh_helper` script being pointed to in the æther.
**Participating in development** Are you willing to test an unreleased engineering code?
* Sure, I can test an experiemental package. I've run Debian Sid since 1999. What's _one more_ unstable package?!?
* I also run a ZFS root filesystem; so `zfs rollback` is useful.
**Contacting you** How can ISC reach you to discuss this matter further?
* Via GitLab is preferred; I'll also link my GitHub account here if possible.backlog