ISC Open Source Projects issueshttps://gitlab.isc.org/groups/isc-projects/-/issues2020-02-04T13:00:12Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/127Rename app-kea-daemons-tabs2020-02-04T13:00:12ZMatthijs Mekkingmatthijs@isc.orgRename app-kea-daemons-tabsIn webui: app-kea-daemons-tabs should be renamed to app-kea-app-tabIn webui: app-kea-daemons-tabs should be renamed to app-kea-app-tabStork-0.4https://gitlab.isc.org/isc-projects/stork/-/issues/140List number of zones per BIND 9 application2020-02-04T13:00:23ZMatthijs Mekkingmatthijs@isc.orgList number of zones per BIND 9 applicationList the number of zones in the detailed application view (type `bind9`).List the number of zones in the detailed application view (type `bind9`).Stork-0.4https://gitlab.isc.org/isc-projects/stork/-/issues/146Make rpc command for rndc2020-02-03T09:17:46ZMatthijs Mekkingmatthijs@isc.orgMake rpc command for rndcSometing like:
```
rpc ForwardRndc(RndcReq) returns (RndcRsp) {}
```Someting like:
```
rpc ForwardRndc(RndcReq) returns (RndcRsp) {}
```Stork-0.4https://gitlab.isc.org/isc-projects/stork/-/issues/118Role-based access, password changes should be documented2020-02-03T10:38:55ZTomek MrugalskiRole-based access, password changes should be documentedWith the #97 merging soon, we need to document the user visible changes introduced:
1. describe the idea behind role-based access
1. explain what roles are currently available (this list is expected to grow significantly over time)
1. u...With the #97 merging soon, we need to document the user visible changes introduced:
1. describe the idea behind role-based access
1. explain what roles are currently available (this list is expected to grow significantly over time)
1. update the section about creating new users (only super-admins, explain group selection)
1. describe how a user can change his own passwordStork-0.4Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/120reenable main dashboard page and show some high level info about apps2020-01-10T17:04:37ZMichal Nowikowskireenable main dashboard page and show some high level info about appsStork-0.3Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/114enable more checks from golangci-lint2020-01-13T13:01:29ZMichal Nowikowskienable more checks from golangci-lintStork-0.4https://gitlab.isc.org/isc-projects/stork/-/issues/32CD (Continuous Delivery) - develop automated deployment to stork.lab.isc.org2020-06-22T08:29:23ZTomek MrugalskiCD (Continuous Delivery) - develop automated deployment to stork.lab.isc.orgDuring exec discussions about Stork, there was a request from Sales team to have something useful for a kind of demo system. We're still several months away from having anything useful enough to be users worthy, but we should start think...During exec discussions about Stork, there was a request from Sales team to have something useful for a kind of demo system. We're still several months away from having anything useful enough to be users worthy, but we should start thinking about our processes to deploy master (or perhaps selected builds) to stork.lab.isc.org.
The goal of this issue to came up with:
1. some rules proposal when to deploy updated code (every commit to master, every commit that passed jenkins tests, perhaps only manually?)
2. develop scripts that will make the deployment possible.Stork-0.3Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/110Fetching HA status from the selected Kea server2020-01-08T18:13:31ZMarcin SiodelskiFetching HA status from the selected Kea serverFollowing the #109, we should send `status-get` command to HA enabled services to fetch their HA status and display it. This introduces changes both in the server and in the UI. One of the options is to create a `<app-ha-status>` compone...Following the #109, we should send `status-get` command to HA enabled services to fetch their HA status and display it. This introduces changes both in the server and in the UI. One of the options is to create a `<app-ha-status>` component which will show the HA status and can be embedded on different pages, e.g. service page or dashboard page....Stork-0.3Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/stork/-/issues/109Generic mechanism to send commands from Stork to Kea via Stork Agent2019-12-27T12:48:15ZMarcin SiodelskiGeneric mechanism to send commands from Stork to Kea via Stork AgentThe issue #51 requires that Stork server can initiate commands to the Kea instance to fetch instance's configuration and then to fetch the HA status using the `status-get` command. This issue is about adding such generic mechanism to sen...The issue #51 requires that Stork server can initiate commands to the Kea instance to fetch instance's configuration and then to fetch the HA status using the `status-get` command. This issue is about adding such generic mechanism to send commands to the selected service via the Stork Argent.Stork-0.3https://gitlab.isc.org/isc-projects/bind9/-/issues/110libirs: Errors raised while parsing resolv.conf are ignored2018-03-19T22:18:15ZMichał Kępieńlibirs: Errors raised while parsing resolv.conf are ignored`irs_resconf_load()` [stores](https://gitlab.isc.org/isc-projects/bind9/blob/e1d6c9a6631f2db967d1a6331b5a177b78e08b89/lib/irs/resconf.c#L569-582) the value returned by `add_search()` into `ret` without consulting its current value first....`irs_resconf_load()` [stores](https://gitlab.isc.org/isc-projects/bind9/blob/e1d6c9a6631f2db967d1a6331b5a177b78e08b89/lib/irs/resconf.c#L569-582) the value returned by `add_search()` into `ret` without consulting its current value first. This causes any previous errors raised while parsing `resolv.conf` to be ignored as long as any `domain` or `search` statement is present in the file.BIND-9.13.0Michał KępieńMichał Kępieńhttps://gitlab.isc.org/isc-projects/kea/-/issues/27CqlHostDataSource::del4 () and del6() fail when given a non-existent host res...2018-11-28T09:21:55ZThomas MarkwalderCqlHostDataSource::del4 () and del6() fail when given a non-existent host reservationNeither function checks for the case of host not found, and causes the server to SIGABRT. They should both be modified to simply return true if the host does not exist. This is in keeping with our philosophy that attempting to delete an...Neither function checks for the case of host not found, and causes the server to SIGABRT. They should both be modified to simply return true if the host does not exist. This is in keeping with our philosophy that attempting to delete an object that does not exist equates to a successful delete.
There are apparently no unit tests for this scenario and there most certainly should be. We need to verify that MySQL and PostgreSQL behave properly and have unit tests for this.Kea1.5-beta2Marcin SiodelskiMarcin Siodelskihttps://gitlab.isc.org/isc-projects/bind9/-/issues/111GitLab CI does not run unit tests2018-03-09T16:29:53ZMichał KępieńGitLab CI does not run unit testsGitLab CI currently `./configure`s BIND [without ATF support](https://gitlab.isc.org/isc-projects/bind9/blob/e1d6c9a6631f2db967d1a6331b5a177b78e08b89/.gitlab-ci.yml#L88), which prevents unit tests from being executed upon each CI run.
S...GitLab CI currently `./configure`s BIND [without ATF support](https://gitlab.isc.org/isc-projects/bind9/blob/e1d6c9a6631f2db967d1a6331b5a177b78e08b89/.gitlab-ci.yml#L88), which prevents unit tests from being executed upon each CI run.
Sadly, ATF is not widely packaged: in the case of Debian, which is of particular interest given that it is the only OS our CI setup uses right now, there have been [several](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766576) [attempts](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773277) to package ATF, but it looks like they did not end with ATF packages getting accepted into official Debian repositories.
Thus, we have two options:
* put a precompiled ATF release into in all of our Docker images (more work to prepare, but saves time upon each CI run),
* compile the ATF version shipped with BIND upon each CI run (easier, but a lot of CPU power goes to waste due to recompiling ATF code over and over).
I ruled out packaging ATF ourselves as I hardly doubt the benefits will outweigh the work we would need to put into it.Ondřej SurýOndřej Surýhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/113update util/bind.sh to reflect BIND9 repo branch renamed to main2022-01-03T18:54:27ZThomas Markwalderupdate util/bind.sh to reflect BIND9 repo branch renamed to mainBIND9 renamed the master branch to main. This change needs to be reflected in util/bind.shBIND9 renamed the master branch to main. This change needs to be reflected in util/bind.sh4.4.3-beta1Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/bind9/-/issues/112MX checks are not applied to dynamic updates2018-03-19T22:18:39ZMichał KępieńMX checks are not applied to dynamic updatesThe `check_mx()` function in `lib/ns/update.c` [incorrectly](https://gitlab.isc.org/isc-projects/bind9/blob/e1d6c9a6631f2db967d1a6331b5a177b78e08b89/lib/ns/update.c#L1740) [tests](https://gitlab.isc.org/isc-projects/bind9/blob/e1d6c9a663...The `check_mx()` function in `lib/ns/update.c` [incorrectly](https://gitlab.isc.org/isc-projects/bind9/blob/e1d6c9a6631f2db967d1a6331b5a177b78e08b89/lib/ns/update.c#L1740) [tests](https://gitlab.isc.org/isc-projects/bind9/blob/e1d6c9a6631f2db967d1a6331b5a177b78e08b89/lib/ns/update.c#L1749) whether the `DNS_RDATA_CHECKMX`/`DNS_RDATA_CHECKMXFAIL` flags are set for each applied MX record update as these flags are never set in code paths related to dynamic updates; they can only be set when loading a zone from a master file (`DNS_ZONEOPT_CHECKMX` → `DNS_MASTER_CHECKMX` → `DNS_RDATA_CHECKMX`). This flaw allows MX records containing IP addresses to be added to a zone even when `check-mx fail;` is used.BIND-9.13.0Michał KępieńMichał Kępieńhttps://gitlab.isc.org/isc-projects/kea/-/issues/112distcheck failure2018-11-05T10:13:33ZWlodzimierz Wenceldistcheck failuredistcheck reporting error:
```
[ubuntu-64-latest] make[4]: Leaving directory '/home/jenkins/workspace/kea-master-distcheck/src/lib/eval'
[ubuntu-64-latest] (cd dhcpsrv && make top_distdir=../../../kea-1.4.0-git distdir=../../../kea-1....distcheck reporting error:
```
[ubuntu-64-latest] make[4]: Leaving directory '/home/jenkins/workspace/kea-master-distcheck/src/lib/eval'
[ubuntu-64-latest] (cd dhcpsrv && make top_distdir=../../../kea-1.4.0-git distdir=../../../kea-1.4.0-git/src/lib/dhcpsrv \
[ubuntu-64-latest] am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
[ubuntu-64-latest] make[4]: Entering directory '/home/jenkins/workspace/kea-master-distcheck/src/lib/dhcpsrv'
[ubuntu-64-latest] make[4]: *** No rule to make target 'parsers/dbaccess_parser.cc', needed by 'distdir'. Stop.
[ubuntu-64-latest] make[4]: Leaving directory '/home/jenkins/workspace/kea-master-distcheck/src/lib/dhcpsrv'
[ubuntu-64-latest] Makefile:531: recipe for target 'distdir' failed
[ubuntu-64-latest] make[3]: *** [distdir] Error 1
[ubuntu-64-latest] make[3]: Leaving directory '/home/jenkins/workspace/kea-master-distcheck/src/lib'
[ubuntu-64-latest] Makefile:526: recipe for target 'distdir' failed
[ubuntu-64-latest] make[2]: *** [distdir] Error 1
[ubuntu-64-latest] make[2]: Leaving directory '/home/jenkins/workspace/kea-master-distcheck/src'
[ubuntu-64-latest] Makefile:715: recipe for target 'distdir' failed
[ubuntu-64-latest] make[1]: *** [distdir] Error 1
[ubuntu-64-latest] make[1]: Leaving directory '/home/jenkins/workspace/kea-master-distcheck'
[ubuntu-64-latest] Makefile:814: recipe for target 'dist' failed
[ubuntu-64-latest] make: *** [dist] Error 2
```Kea1.5-beta1https://gitlab.isc.org/isc-projects/dhcp/-/issues/114Update BIND9 to current 9.11.192022-01-12T14:06:54ZThomas MarkwalderUpdate BIND9 to current 9.11.19We currently build against 9.11.14, see if we can update.We currently build against 9.11.14, see if we can update.4.4.3-beta1Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/bind9/-/issues/113Minor testsummary.sh improvements (handling colored output, failure summary)2020-09-16T10:05:12ZMichał KępieńMinor testsummary.sh improvements (handling colored output, failure summary)`bin/tests/system/testsummary.sh` could be slightly improved, so that it:
* correctly processes colored system test output,
* prints a summary of failed system tests, if any.`bin/tests/system/testsummary.sh` could be slightly improved, so that it:
* correctly processes colored system test output,
* prints a summary of failed system tests, if any.BIND-9.13.0Michał KępieńMichał Kępieńhttps://gitlab.isc.org/isc-projects/stork/-/issues/115get config and hooks from kea by server via agent2023-07-06T09:33:33ZMichal Nowikowskiget config and hooks from kea by server via agentRef: #40Ref: #40Stork-0.3Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/bind9/-/issues/114Out of tree system tests2020-10-02T08:41:05ZEvan HuntOut of tree system testsAn submitted by @pemensik and addressed in !82An submitted by @pemensik and addressed in !82October 2020 (9.11.24, 9.11.24-S1, 9.16.8, 9.16.8-S1, 9.17.6)https://gitlab.isc.org/isc-projects/dhcp/-/issues/116keama compilation on Fedora 32 fails2020-07-30T12:32:00ZMichal Nowikowskikeama compilation on Fedora 32 fails```
gcc -g -O2 -Wall -Werror -fno-strict-aliasing -I../includes -I/vagrant/bind/include -o keama keama.o data.o conflex.o json.o confparse.o parse.o options.o reduce.o print.o eval.o
/usr/bin/ld: conflex.o:/vagrant/keama/keama.h:...```
gcc -g -O2 -Wall -Werror -fno-strict-aliasing -I../includes -I/vagrant/bind/include -o keama keama.o data.o conflex.o json.o confparse.o parse.o options.o reduce.o print.o eval.o
/usr/bin/ld: conflex.o:/vagrant/keama/keama.h:61: multiple definition of `parses'; keama.o:/vagrant/keama/keama.h:61: first defined here
/usr/bin/ld: conflex.o:/vagrant/keama/keama.h:38: multiple definition of `resolve'; keama.o:/vagrant/keama/keama.h:38: first defined here
/usr/bin/ld: json.o:/vagrant/keama/keama.h:61: multiple definition of `parses'; keama.o:/vagrant/keama/keama.h:61: first defined here
/usr/bin/ld: json.o:/vagrant/keama/keama.h:38: multiple definition of `resolve'; keama.o:/vagrant/keama/keama.h:38: first defined here
/usr/bin/ld: confparse.o:/vagrant/keama/keama.h:61: multiple definition of `parses'; keama.o:/vagrant/keama/keama.h:61: first defined here
/usr/bin/ld: confparse.o:/vagrant/keama/keama.h:38: multiple definition of `resolve'; keama.o:/vagrant/keama/keama.h:38: first defined here
/usr/bin/ld: parse.o:/vagrant/keama/keama.h:38: multiple definition of `resolve'; keama.o:/vagrant/keama/keama.h:38: first defined here
/usr/bin/ld: parse.o:/vagrant/keama/keama.h:61: multiple definition of `parses'; keama.o:/vagrant/keama/keama.h:61: first defined here
/usr/bin/ld: options.o:/vagrant/keama/keama.h:61: multiple definition of `parses'; keama.o:/vagrant/keama/keama.h:61: first defined here
/usr/bin/ld: options.o:/vagrant/keama/keama.h:38: multiple definition of `resolve'; keama.o:/vagrant/keama/keama.h:38: first defined here
/usr/bin/ld: reduce.o:/vagrant/keama/keama.h:61: multiple definition of `parses'; keama.o:/vagrant/keama/keama.h:61: first defined here
/usr/bin/ld: reduce.o:/vagrant/keama/keama.h:38: multiple definition of `resolve'; keama.o:/vagrant/keama/keama.h:38: first defined here
/usr/bin/ld: print.o:/vagrant/keama/keama.h:61: multiple definition of `parses'; keama.o:/vagrant/keama/keama.h:61: first defined here
/usr/bin/ld: print.o:/vagrant/keama/keama.h:38: multiple definition of `resolve'; keama.o:/vagrant/keama/keama.h:38: first defined here
/usr/bin/ld: eval.o:/vagrant/keama/keama.h:61: multiple definition of `parses'; keama.o:/vagrant/keama/keama.h:61: first defined here
/usr/bin/ld: eval.o:/vagrant/keama/keama.h:38: multiple definition of `resolve'; keama.o:/vagrant/keama/keama.h:38: first defined here
collect2: error: ld returned 1 exit status
```Francis DupontFrancis Dupont