stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2024-03-04T19:25:10Zhttps://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/1300Check the minimum Java version in build system and describe it in docs2024-02-13T14:52:11ZSlawek FigielCheck the minimum Java version in build system and describe it in docsThe issue was found by @marcin during 1.15 sanity checks: https://gitlab.isc.org/isc-projects/stork/-/issues/1296#note_434164
The current version of the OpenAPI generator requires at least OpenJRE 11. The build system checks only if the...The issue was found by @marcin during 1.15 sanity checks: https://gitlab.isc.org/isc-projects/stork/-/issues/1296#note_434164
The current version of the OpenAPI generator requires at least OpenJRE 11. The build system checks only if the `java` binary is present and the documentation specifies that Java is required without providing a minimum version.
We should somehow cover the java requirement checks in the rake files or/and the docs.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1293UI code coverage2024-02-13T14:38:49ZSlawek FigielUI code coverageWe have a utility to generate coverage for the backend but not for the frontend. We should fill this gap.
The development of this feature was excluded from #800.We have a utility to generate coverage for the backend but not for the frontend. We should fill this gap.
The development of this feature was excluded from #800.1.16https://gitlab.isc.org/isc-projects/stork/-/issues/1292Restore storybook plugins2024-02-13T14:37:10ZSlawek FigielRestore storybook pluginsDue to compatibility problems with the dynamic forms in Angular, we turned off some default Storybook plugins some time ago. We should restore them because they are pretty useful.
List of disabled plugins:
- `@storybook/addon-controls`...Due to compatibility problems with the dynamic forms in Angular, we turned off some default Storybook plugins some time ago. We should restore them because they are pretty useful.
List of disabled plugins:
- `@storybook/addon-controls`
- `@storybook/addon-actions`
This code was implemented originally in #800, but it is out-of-scope of that issue.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1288404 if stork-server is installed in custom path2024-02-06T14:53:55ZAndrei Pavelandrei@isc.org404 if stork-server is installed in custom pathSteps
1. Install server in a custom location.
```sh
$ rake install:server DEST=/opt/stork-server
mkdir -p /opt/stork-server
cp -a -f dist/server/. /opt/stork-server
```
2. Start server.
```sh
$ stork-server
WARN[2024-01-30 15:16:24]...Steps
1. Install server in a custom location.
```sh
$ rake install:server DEST=/opt/stork-server
mkdir -p /opt/stork-server
cp -a -f dist/server/. /opt/stork-server
```
2. Start server.
```sh
$ stork-server
WARN[2024-01-30 15:16:24] restservice.go:354 Cannot read the base URL in the '/usr/share/stork/www/index.html' file because it is missing. If the files are located on separate machine, you need manually change the 'href' value of the <base> HTML tag to '/' error="open /usr/share/stork/www/index.html: no such file or directory"
```
3. Attempt to open the UI in browser.
> 404 page not found
Expectation was that I get served `/opt/stork-server/usr/share/stork/www/index.html` which exists.
---
Similarly, stork-server logs on startup:
```
WARN[2024-01-30 15:16:24] server.go:102 The hook directory: '/var/lib/stork-server/hooks' doesn't exist error="cannot find plugin paths in: /var/lib/stork-server/hooks: cannot list hook directory: /var/lib/stork-server/hooks: open /var/lib/stork-server/hooks: no such file or directory"
```
It would be nice if this was also looked up from the installation path and that the directory would be created on installation, so there would be no warnings by default.
This last one also happens with stork-agent.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1285Update project dependencies2024-02-05T18:03:23ZSlawek FigielUpdate project dependenciesWe should update Go, JavaScript, Python, and so on dependencies to fix bugs and security vulnerabilities.We should update Go, JavaScript, Python, and so on dependencies to fix bugs and security vulnerabilities.1.15Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1264CodeQL: Python issues2024-02-02T11:56:23ZTomek MrugalskiCodeQL: Python issuesCodeQL reports [13 issues in the Python](https://github.com/isc-projects/stork/security/code-scanning?query=is%3Aopen+branch%3Amaster+language%3Apython) code. 3 of them are errors, 1 warning, remaining are notes related to tests. Neverth...CodeQL reports [13 issues in the Python](https://github.com/isc-projects/stork/security/code-scanning?query=is%3Aopen+branch%3Amaster+language%3Apython) code. 3 of them are errors, 1 warning, remaining are notes related to tests. Nevertheless it's useful to address them, so the security report on github is cleaner and has less noise.1.15Tomek MrugalskiTomek Mrugalskihttps://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/1254Ubuntu 20.04 LTS compatibility for LDAP hook2024-01-08T16:48:23ZSlawek FigielUbuntu 20.04 LTS compatibility for LDAP hookThe issue was reported on our mailing list: [Link](https://lists.isc.org/pipermail/stork-users/2023-December/000238.html).
We restored the Ubuntu 20.04 LTS support for main Stork binaries in the 1.14 release, but we forgot about the LDA...The issue was reported on our mailing list: [Link](https://lists.isc.org/pipermail/stork-users/2023-December/000238.html).
We restored the Ubuntu 20.04 LTS support for main Stork binaries in the 1.14 release, but we forgot about the LDAP hook.1.15Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1251LDAP hook: Build fails on some Linux distributions2023-12-19T14:47:34ZSlawek FigielLDAP hook: Build fails on some Linux distributionsThe issue was found by @andrei during 1.14 sanity checks: https://gitlab.isc.org/isc-projects/stork/-/issues/1240#note_421471
```
Another one I had forgotten. I understand that this one as well is not a task that you usually run on a ta...The issue was found by @andrei during 1.14 sanity checks: https://gitlab.isc.org/isc-projects/stork/-/issues/1240#note_421471
```
Another one I had forgotten. I understand that this one as well is not a task that you usually run on a tarball.
rake hook:init MODULE=stork-server-ldap; rake hook:build results in error when run on a tarball. It seems like it is not picking up on DEFAULT_HOOK_DIRECTORY.
rm -f
Removing old compiled hooks...
cp go.mod go.sum /tmp/d20231205-1147463-kn7j49
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/tools/golang/go/bin/go mod edit -replace isc.org/stork=../../../../../Descărcări/sanity-checks/stork-1.14.0/backend
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/tools/golang/go/bin/go mod tidy
rake build
Building stork-server-ldap...
mkdir -p build
rm
rm: missing operand
Try 'rm --help' for more information.
rake aborted!
Command failed with status (1): [rm...]
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/hooks/stork-server-ldap/Rakefile:17:in `block in <top (required)>'
Tasks: TOP => build
(See full trace by running task with --trace)
rake aborted!
Command failed with status (1): [rake build...]
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:150:in `block (4 levels) in <top (required)>'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:141:in `block (3 levels) in <top (required)>'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:66:in `block (3 levels) in forEachHook'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:65:in `chdir'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:65:in `block (2 levels) in forEachHook'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:46:in `chdir'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:46:in `block in forEachHook'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:42:in `foreach'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:42:in `forEachHook'
/home/andrei/Descărcări/sanity-checks/stork-1.14.0/rakelib/90_hooks.rake:139:in `block (2 levels) in <top (required)>'
Tasks: TOP => hook:build
(See full trace by running task with --trace)
```1.16https://gitlab.isc.org/isc-projects/stork/-/issues/1250Syncing a new hook directory fails when running from tarball2023-12-19T14:43:29ZSlawek FigielSyncing a new hook directory fails when running from tarballThe issue was found by @andrei during 1.14 sanity checks: https://gitlab.isc.org/isc-projects/stork/-/issues/1240#note_421415
* If I do `rake hook:init MODULE=stork-server-ldap`, it initializes the git module correctly relative to the t...The issue was found by @andrei during 1.14 sanity checks: https://gitlab.isc.org/isc-projects/stork/-/issues/1240#note_421415
* If I do `rake hook:init MODULE=stork-server-ldap`, it initializes the git module correctly relative to the tarball content. However, if I do `rake hook:sync`, because the tarball is not a git repo, it goes all the way to the nearest parent git repository, and does some syncing there. I happen to have my home directory set up as a git repo, so I ended up with having some of my modules there modified. The task could instead check if there is a `.git` directory created at the same level as `Rakefile` first to determine if it is a tarball or a git repo. I also understand that this is not a task that you usually run on a tarball.
```
modified: .config/awesome/lain (new commits, modified content)
modified: .zprezto (modified content)
```backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1249Problem installing danger on operating system with non-US locale2023-12-19T14:42:10ZSlawek FigielProblem installing danger on operating system with non-US localeThe issue was found by @andrei during 1.14 sanity checks: https://gitlab.isc.org/isc-projects/stork/-/issues/1240#note_421412
* I could not run system tests. I get this error on `rake systemtest`. Not sure what is wrong. Sounds like an ...The issue was found by @andrei during 1.14 sanity checks: https://gitlab.isc.org/isc-projects/stork/-/issues/1240#note_421412
* I could not run system tests. I get this error on `rake systemtest`. Not sure what is wrong. Sounds like an encoding could be enforced somewhere.
```
143.7 Bundler version 2.3.26
143.7 /app/tools/ruby/bin/bundle install --gemfile /app/rakelib/init_deps/danger/Gemfile --path /app/tools/ruby --binstubs /app/tools/ruby/bin_bundle
143.7 Preparing: /app/tools/ruby/bin_bundle/danger...
143.7 mkdir -p /app/tools/ruby/bin_bundle
143.9 /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/yaml_serializer.rb:54:in `split': invalid byte sequence in US-ASCII (ArgumentError)
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/yaml_serializer.rb:54:in `load'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/settings.rb:459:in `block in load_config'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/shared_helpers.rb:103:in `filesystem_access'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/settings.rb:455:in `load_config'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/settings.rb:91:in `initialize'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler.rb:342:in `new'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler.rb:342:in `settings'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/env.rb:20:in `report'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/friendly_errors.rb:74:in `request_issue_report_for'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/friendly_errors.rb:53:in `log_error'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/friendly_errors.rb:126:in `rescue in with_friendly_errors'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/friendly_errors.rb:118:in `with_friendly_errors'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/exe/bundle:36:in `<top (required)>'
143.9 from /app/tools/ruby/bin/bundle:25:in `load'
143.9 from /app/tools/ruby/bin/bundle:25:in `<main>'
143.9 /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/yaml_serializer.rb:54:in `split': invalid byte sequence in US-ASCII (ArgumentError)
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/yaml_serializer.rb:54:in `load'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/settings.rb:459:in `block in load_config'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/shared_helpers.rb:103:in `filesystem_access'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/settings.rb:455:in `load_config'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/settings.rb:91:in `initialize'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler.rb:342:in `new'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler.rb:342:in `settings'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/cli.rb:66:in `initialize'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/vendor/thor/lib/thor.rb:388:in `new'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/vendor/thor/lib/thor.rb:388:in `dispatch'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/cli.rb:31:in `dispatch'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/cli.rb:25:in `start'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/exe/bundle:48:in `block in <top (required)>'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/lib/bundler/friendly_errors.rb:120:in `with_friendly_errors'
143.9 from /app/tools/ruby/gems/bundler-2.3.26/exe/bundle:36:in `<top (required)>'
143.9 from /app/tools/ruby/bin/bundle:25:in `load'
143.9 from /app/tools/ruby/bin/bundle:25:in `<main>'
143.9 rake aborted!
143.9 Command failed with status (1): [/app/tools/ruby/bin/bundle install --gemfi...]
143.9 /app/rakelib/00_init.rake:795:in `block in <top (required)>'
143.9 /app/rakelib/00_init.rake:133:in `block in find_and_prepare_deps'
143.9 /app/rakelib/00_init.rake:115:in `each'
143.9 /app/rakelib/00_init.rake:115:in `find_and_prepare_deps'
143.9 /app/rakelib/00_init.rake:1113:in `block in <top (required)>'
143.9 Tasks: TOP => /app/tools/ruby/bin_bundle/danger
143.9 (See full trace by running task with --trace)
```backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1245Deprecation warning in mockery2023-12-19T14:37:31ZSlawek FigielDeprecation warning in mockeryThe issue was found by @piotrek during [1.14 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1240#note_421364).
```shell
$ rake unittest:backend
WRN DEPRECATION: use of the packages config will be the only way to gener...The issue was found by @piotrek during [1.14 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1240#note_421364).
```shell
$ rake unittest:backend
WRN DEPRECATION: use of the packages config will be the only way to generate mocks in v3. Please migrate your config to use the packages feature. dry-run=false migration=https://vektra.github.io/mockery/v2.34/migrating_to_packages/ url=https://vektra.github.io/mockery/v2.34/features/#packages-configuration version=v2.34.0
```backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1238Redundant asterisks in Changelog after merge2023-12-04T11:10:02ZSlawek FigielRedundant asterisks in Changelog after mergeThe entry header is incorrect. It contains an unnecessary asterisk.
![image](/uploads/d5ba0ef87fcad47256ed3318026cc7ff/image.png)The entry header is incorrect. It contains an unnecessary asterisk.
![image](/uploads/d5ba0ef87fcad47256ed3318026cc7ff/image.png)https://gitlab.isc.org/isc-projects/stork/-/issues/1234Update the build from sources guide for Ubuntu 20.04 LTS2024-02-06T14:42:33ZSlawek FigielUpdate the build from sources guide for Ubuntu 20.04 LTSSince the Stork build system requires Python 3.10 and Ruby 2.3, [the guide to build Stork from sources](https://gitlab.isc.org/isc-projects/stork/-/wikis/Install) is no longer applicable on Ubuntu 20.04 LTS.
The guide recommends install...Since the Stork build system requires Python 3.10 and Ruby 2.3, [the guide to build Stork from sources](https://gitlab.isc.org/isc-projects/stork/-/wikis/Install) is no longer applicable on Ubuntu 20.04 LTS.
The guide recommends installing Python and Ruby from the package repository, but the available versions of the above dependencies are outdated. Users need to install Python and Ruby from their maintainers' external, official packages. We should mention it in the guide.1.16https://gitlab.isc.org/isc-projects/stork/-/issues/1233Upgrade vulnerable packages before 1.14 release2023-11-30T17:21:36ZMarcin SiodelskiUpgrade vulnerable packages before 1.14 releaseThe UI and the backend audits show some vulnerabilities we want to fix before the 1.14 release.The UI and the backend audits show some vulnerabilities we want to fix before the 1.14 release.1.14Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/1231Can't install stork on Openbsd2023-12-12T02:16:15ZmikygeeCan't install stork on OpenbsdHello,
Last year I participated on this topic
https://gitlab.isc.org/isc-projects/stork/-/issues/193
I'm reinstalling my DNS server on Openbsd and can't build the stork agent
```
# rake32 build:agent --trace
ERROR: Unknown/unsupported ...Hello,
Last year I participated on this topic
https://gitlab.isc.org/isc-projects/stork/-/issues/193
I'm reinstalling my DNS server on Openbsd and can't build the stork agent
```
# rake32 build:agent --trace
ERROR: Unknown/unsupported architecture: amd64
rake aborted!
/home/mikael/stork/rakelib/00_init.rake:509:in `<top (required)>'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/rake_module.rb:29:in `load'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/rake_module.rb:29:in `load_rakefile'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/default_loader.rb:11:in `load'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/application.rb:788:in `load_imports'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/application.rb:718:in `raw_load_rakefile'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/application.rb:104:in `block in load_rakefile'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/application.rb:186:in `standard_exception_handling'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/application.rb:103:in `load_rakefile'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/application.rb:82:in `block in run'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/application.rb:186:in `standard_exception_handling'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/lib/rake/application.rb:80:in `run'
/usr/local/lib/ruby/gems/3.2/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/usr/local/bin/rake32:25:in `load'
/usr/local/bin/rake32:25:in `<main>'
```
My system is like this
```
# uname -a
OpenBSD machinename.domain.org 7.4 GENERIC.MP#0 amd64
```
So I when to rakelib/00_init.rake line 501 and added a switch for "when "amd64"
```
uname_arch=`uname -m`
case uname_arch.rstrip
when "x86_64"
ARCH="amd64"
when "amd64"
ARCH="amd64"
when "aarch64_be", "aarch64", "armv8b", "armv8l"
ARCH="arm64"
else
puts "ERROR: Unknown/unsupported architecture: #{uname_arch}"
fail
end
```
Then it works
Also, why is it trying to download protoc or protobug although it's already installed on my system
```
# pkg_info | grep protobuf
protobuf-3.21.12p0 c++ protocol buffers
```
```
# rake32 build:agent
/usr/local/bin/go install google.golang.org/protobuf/cmd/protoc-gen-go@v1.31.0
/usr/local/bin/protoc-gen-go --version
protoc-gen-go v1.31.0
/usr/local/bin/go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@v1.3.0
go: downloading google.golang.org/grpc v1.3.0
go: downloading google.golang.org/grpc/cmd/protoc-gen-go-grpc v1.3.0
go: downloading google.golang.org/protobuf v1.28.1
/usr/local/bin/protoc-gen-go-grpc --version
protoc-gen-go-grpc 1.3.0
/usr/local/bin/protoc --proto_path=. --go_out=. --go-grpc_out=. agent.proto
/usr/local/bin/go build -ldflags=-X 'isc.org/stork.BuildDate=2023-11-26 14:25'
go: downloading github.com/urfave/cli/v2 v2.25.7
go: downloading github.com/cpuguy83/go-md2man/v2 v2.0.2
go: downloading github.com/xrash/smetrics v0.0.0-20201216005158-039620a65673
go: downloading github.com/pkg/errors v0.9.1
go: downloading github.com/russross/blackfriday/v2 v2.1.0
Stork Code Gen build date: 2023-11-26 14:25 (timestamp: 231126142545)
backend/cmd/stork-code-gen/stork-code-gen std-option-defs --input codegen/std_dhcpv4_option_def.json --output backend/appcfg/kea/stdoptiondef4.go --template backend/appcfg/kea/stdoptiondef4.go.template
/usr/local/bin/go fmt ./appcfg/kea/...
go: downloading muzzammil.xyz/jsonc v1.0.0
go: downloading github.com/apparentlymart/go-cidr v1.1.0
go: downloading github.com/sirupsen/logrus v1.9.3
go: downloading golang.org/x/term v0.12.0
go: downloading golang.org/x/sys v0.12.0
appcfg/kea/stdoptiondef4.go
backend/cmd/stork-code-gen/stork-code-gen std-option-defs --input codegen/std_dhcpv6_option_def.json --output backend/appcfg/kea/stdoptiondef6.go --template backend/appcfg/kea/stdoptiondef6.go.template
/usr/local/bin/go fmt ./appcfg/kea/...
appcfg/kea/stdoptiondef6.go
/usr/local/bin/go build -ldflags=-X 'isc.org/stork.BuildDate=2023-11-26 14:25'
go: downloading github.com/Showmax/go-fqdn v1.0.0
go: downloading github.com/prometheus/client_golang v1.16.0
go: downloading github.com/prometheus/common v0.44.0
go: downloading github.com/shirou/gopsutil v3.21.11+incompatible
go: downloading google.golang.org/grpc v1.58.2
go: downloading google.golang.org/grpc/security/advancedtls v0.0.0-20230925230705-147bd8591213
go: downloading github.com/beorn7/perks v1.0.1
go: downloading github.com/cespare/xxhash/v2 v2.2.0
go: downloading github.com/prometheus/client_model v0.4.0
go: downloading github.com/prometheus/procfs v0.12.0
go: downloading golang.org/x/net v0.15.0
go: downloading golang.org/x/crypto v0.13.0
go: downloading github.com/matttproud/golang_protobuf_extensions v1.0.4
go: downloading github.com/tklauser/go-sysconf v0.3.12
go: downloading github.com/golang/protobuf v1.5.3
go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20230920204549-e6e6cdab5c13
go: downloading golang.org/x/text v0.13.0
touch -c backend/cmd/stork-agent/stork-agent
Stork Agent build date: 2023-11-26 14:25 (timestamp: 231126142545)
```
Thank you1.14Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1227Put hook binaries outside /var by default2024-02-02T12:57:44ZSlawek FigielPut hook binaries outside /var by defaultThe problem was reported [on our mailing list](https://lists.isc.org/pipermail/stork-users/2023-November/000231.html).
The default hook directories are `/var/lib/stork-agent/hooks` and `/var/lib/stork-server/hooks`.
But the various Linu...The problem was reported [on our mailing list](https://lists.isc.org/pipermail/stork-users/2023-November/000231.html).
The default hook directories are `/var/lib/stork-agent/hooks` and `/var/lib/stork-server/hooks`.
But the various Linux distros in the `enforcing` mode disallow the libraries from the `/var` directory.
It causes the Stork hooks not to be loaded, producing the message: `failed to map segment from shared object`.1.16https://gitlab.isc.org/isc-projects/stork/-/issues/1201Stork 1.13.0 not working on Ubuntu 20.04.6. LTS2023-12-06T18:32:23ZThomas MaurerStork 1.13.0 not working on Ubuntu 20.04.6. LTS---
name: Stork 1.13.0 not working on Ubuntu 20.04.6. LTS
about: `isc-stork-server`
---
**Describe the bug**
Stork V1.13.0 requires GLIBC_2.32 or newer. But on Ubuntu 20.04.6 LTS (focal) only 2.31 is available. However in the Documenta...---
name: Stork 1.13.0 not working on Ubuntu 20.04.6. LTS
about: `isc-stork-server`
---
**Describe the bug**
Stork V1.13.0 requires GLIBC_2.32 or newer. But on Ubuntu 20.04.6 LTS (focal) only 2.31 is available. However in the Documentation (https://stork.readthedocs.io/en/v1.13.0/install.html#supported-systems) Ubuntu 18.04 and 20.04 are reportet to work.
**To Reproduce**
Steps to reproduce the behavior:
1. Update stork to V1.13.0
2. Stork does not Start
3. in var/log/syslog is see:
Oct 16 08:26:34 sbcc-dhcp-0101 stork-server[1557772]: /usr/bin/stork-server: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /usr/bin/stork-server)
Oct 16 08:26:34 sbcc-dhcp-0101 stork-server[1557772]: /usr/bin/stork-server: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /usr/bin/stork-server)
Oct
**Expected behavior**
Update the Documentation or update the dependencies for Stork to run on Ubuntu 20.04
**Environment:**
- Kea version: 2.0.3
tarball
linked with:
log4cplus 1.1.2
OpenSSL 1.1.1f 31 Mar 2020
database:
MySQL backend 12.0, library 8.0.34
PostgreSQL backend 6.2, library 120016
Memfile backend 2.1
- Stork: 1.13.0.231011103556
- OS: Ubuntu 20.04.6 LTS
**Contacting you**
Feel free to contact me via E-Mail1.14Slawek FigielSlawek Figiel