ISC Open Source Projects issueshttps://gitlab.isc.org/groups/isc-projects/-/issues2020-10-26T13:23:20Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/1494Issues with 0auth2020-10-26T13:23:20Zrelease changes scriptIssues with 0authhttps://gitlab.isc.org/isc-projects/kea/-/issues/1492more explicit messages for log4cplus & boost missing dependencies2020-11-16T11:27:42ZAndrei Pavelandrei@isc.orgmore explicit messages for log4cplus & boost missing dependenciesIf you are missing log4cplus or boost headers on your machine, you are only met with the message `Missing required header files` omitting which headers are actually missing. Let's specify explicitly what is missing, as is the case with o...If you are missing log4cplus or boost headers on your machine, you are only met with the message `Missing required header files` omitting which headers are actually missing. Let's specify explicitly what is missing, as is the case with other dependencies.
Minor change required. Two lines in `configure.ac` & `m4macros/ax_boost_for_kea.m4`.kea1.9.2Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/kea/-/issues/1491spin-off from #1298: add "option-data" examples for space 4o6 all-options.json2020-11-12T19:50:55ZAndrei Pavelandrei@isc.orgspin-off from #1298: add "option-data" examples for space 4o6 all-options.jsonSpace `4o6` seems to be the only non-standard, defined-in-kea option space that has missing options from `doc/examples/kea6/all-options.json`. Maybe add them as well.
```
/* DHCPv4-over-DHCPv6 (RFC 7341) inter-process communication. Thes...Space `4o6` seems to be the only non-standard, defined-in-kea option space that has missing options from `doc/examples/kea6/all-options.json`. Maybe add them as well.
```
/* DHCPv4-over-DHCPv6 (RFC 7341) inter-process communication. These are option
codes for the ISC vendor specific options used in 4o6 */
static const uint16_t ISC_V6_4O6_INTERFACE = 60000;
static const uint16_t ISC_V6_4O6_SRC_ADDRESS = 60001;
static const uint16_t ISC_V6_4O6_SRC_PORT = 60002;
```Andrei Pavelandrei@isc.orgAndrei Pavelandrei@isc.orghttps://gitlab.isc.org/isc-projects/kea/-/issues/1490spin-off from #1298: add tests for options with negative values2022-11-02T15:10:18ZAndrei Pavelandrei@isc.orgspin-off from #1298: add tests for options with negative valuesIt became apparent while working on #1298 that options can have negative values. Specifically the ones with `OPT_INT[0-9]+_TYPE` as opposed to `OPT_UINT[0-9]+_TYPE`.
And it became apparent that we don't have any tests validating that t...It became apparent while working on #1298 that options can have negative values. Specifically the ones with `OPT_INT[0-9]+_TYPE` as opposed to `OPT_UINT[0-9]+_TYPE`.
And it became apparent that we don't have any tests validating that the value is parsed correctly, without errors, etc.
Let's add some.backloghttps://gitlab.isc.org/isc-projects/bind9/-/issues/2234Add ARM64 build, unit and system test CI jobs2020-10-26T12:30:11ZMichal NowakAdd ARM64 build, unit and system test CI jobsWe used to have ARM64 host before, but it was removed due to it's connectivity problems.
We should add ARM64 CI jobs for two reasons:
1. we support the ARM64 platform and distributions are [actively packaging it](https://gitlab.isc.org...We used to have ARM64 host before, but it was removed due to it's connectivity problems.
We should add ARM64 CI jobs for two reasons:
1. we support the ARM64 platform and distributions are [actively packaging it](https://gitlab.isc.org/isc-projects/bind9/-/issues/2167)
2. Fedora on ARM64 is one of stress test targets and we should ensure that BIND works on this platform before we proceed to later stages of the release process
This requires ARM64 host, possibly AWS, performance-wise we should be close to AMD64 hosts not to block pipelines.
OS platform should be Fedora to match stress test CI jobs.Not plannedhttps://gitlab.isc.org/isc-projects/kea/-/issues/1489Sanity checks for Kea 1.9.1 rc12020-10-28T07:27:56ZMichal NowikowskiSanity checks for Kea 1.9.1 rc1```
We are now at step SANITY CHECKS of Kea 1.9.1 rc1.
Please verify the packages and files according to
https://wiki.isc.org/bin/view/QA/KeaReleaseProcess, "4. Sanity Checks" chapter
and your imagination.
Before starting any checks. pl...```
We are now at step SANITY CHECKS of Kea 1.9.1 rc1.
Please verify the packages and files according to
https://wiki.isc.org/bin/view/QA/KeaReleaseProcess, "4. Sanity Checks" chapter
and your imagination.
Before starting any checks. please, state in Sanity Checks issue in GitLab
what check you are doing in a thread/discussion (not as comment).
When you finish given check state in the same thread/discussion what is the result.
This way we know what is covered upfront and we can avoid repeating ourselves.
Release content is located on:
1) [tarballs] repo.isc.org in the following folders:
/data/shared/sweng/kea/releases/1.9.1-rc1
/data/shared/sweng/kea/releases/premium-1.9.1-rc1
/data/shared/sweng/kea/releases/subscription-1.9.1-rc1
SHA256 (kea-1.9.1.tar.gz) = ece8cc10fafa2aa8bf5cc18f95f4bfb05bd52f8ee6a152d1ee8b53c28a526999
SHA256 (kea-premium-1.9.1.tar.gz) = 572edf5bfc75027e7ee668ea61c6526acdeeb04dc59380f18b3181fff17d70e9
SHA256 (kea-subscription-1.9.1.tar.gz) = d750e39bdbadc72556152247d7a93d21d52ed4ef4692b828cc9f70f2467078c3
2) [rpm/deb packages] on packages.isc.org, exact packages versions are stored here:
https://jenkins.isc.org/job/kea-dev/job/pkg/103/
Release version is 1.9.1-isc0006920201023180203 (please verify if it is this version while installing).
Install instruction is here: https://wiki.isc.org/bin/view/QA/KeaReleaseProcess, chapter 4. Sanity Checks, point 9.
```kea1.9.1https://gitlab.isc.org/isc-projects/bind9/-/issues/2233catalog zone VERSION number in Bv9ARM doesn't match draft's version number2022-05-03T11:26:48ZJP Menscatalog zone VERSION number in Bv9ARM doesn't match draft's version numberI note that the VERSION.$CATZ number in the [Bv9ARM section on catalog zones](https://bind9.readthedocs.io/en/v9_16_7/advanced.html#catalog-zones) insinuates we should use
```
version.catalog.example. IN TXT "1"
```
However, the [d...I note that the VERSION.$CATZ number in the [Bv9ARM section on catalog zones](https://bind9.readthedocs.io/en/v9_16_7/advanced.html#catalog-zones) insinuates we should use
```
version.catalog.example. IN TXT "1"
```
However, the [draft](https://tools.ietf.org/html/draft-ietf-dnsop-dns-catalog-zones-00#section-4.2) specifies
> For this memo, the value of one of the RRs in the "version.$CATZ" TXT RRset MUST be setto "2", i.e.
```
version.$CATZ 0 IN TXT "2"
```
Our friends over at Knot DNS [say](https://www.knot-dns.cz/docs/3.0/html/configuration.html#catalog-zones)
> required to include version record `version 0 IN TXT "2"`
So, my question actually is: does BIND now support version 2 and the documentation could be adjusted, or does BIND effectively (in current versions) support version 1?https://gitlab.isc.org/isc-projects/bind9/-/issues/2232bind9.xsl.h sometimes gets modified during the 'docs' CI job on v9_162023-12-12T11:33:18ZMichal Nowakbind9.xsl.h sometimes gets modified during the 'docs' CI job on v9_16On `v9_16` the `docs` CI jobs [sometimes](https://gitlab.isc.org/isc-projects/bind9/-/jobs/1247836) (not the first time I saw it) modifies `bin/named/bind9.xsl.h` unexpectedly:
```
$ if test "$(git status --porcelain | grep -Ev '\?\?' | ...On `v9_16` the `docs` CI jobs [sometimes](https://gitlab.isc.org/isc-projects/bind9/-/jobs/1247836) (not the first time I saw it) modifies `bin/named/bind9.xsl.h` unexpectedly:
```
$ if test "$(git status --porcelain | grep -Ev '\?\?' | grep -v -F -e aclocal.m4 -e configure -e ltmain.sh -e m4/ | wc -l)" -gt "0"; then git status --short; exit 1; fi
M aclocal.m4
M bin/named/bind9.xsl.h
M configure
M ltmain.sh
M m4/libtool.m4
Cleaning up file based variables
00:00
ERROR: Job failed: exit code 1
```BIND 9.17 Backburnerhttps://gitlab.isc.org/isc-projects/kea/-/issues/1488Backport #1434 (fix HA and lease commands with db backend)2020-11-27T06:38:00ZRazvan BecheriuBackport #1434 (fix HA and lease commands with db backend)Backport #1434 to 1.8.1Backport #1434 to 1.8.1kea1.8.1Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/kea/-/issues/1487Issues with 0auth2020-10-23T16:24:44ZjenkinsIssues with 0authhttps://gitlab.isc.org/isc-projects/kea/-/issues/1486Issues with auth2020-10-23T15:05:33ZjenkinsIssues with authhttps://gitlab.isc.org/isc-projects/kea/-/issues/1485Address Selection Policy options for DHCPv6 (RFC7078)2020-11-12T16:56:42ZTomek MrugalskiAddress Selection Policy options for DHCPv6 (RFC7078)Filed for completeness. We should implement support for RFC7078 one day.
I'm not aware of anyone requesting this.Filed for completeness. We should implement support for RFC7078 one day.
I'm not aware of anyone requesting this.outstandinghttps://gitlab.isc.org/isc-projects/kea/-/issues/1484DHCPv6 options for 802.21 mobility services (RFC5678)2020-11-12T16:56:32ZTomek MrugalskiDHCPv6 options for 802.21 mobility services (RFC5678)This is filed for completeness. There's RFC5678 that we don't seem to support yet.
As of today, I'm not aware of anyone requesting support for those options.This is filed for completeness. There's RFC5678 that we don't seem to support yet.
As of today, I'm not aware of anyone requesting support for those options.outstandinghttps://gitlab.isc.org/isc-projects/kea/-/issues/14831.9.1 release changes2020-10-23T16:51:25ZMichal Nowikowski1.9.1 release changeskea1.9.1Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/kea/-/issues/1482Add support for Internet Storage options (RFC4174)2020-11-12T16:56:27ZTomek MrugalskiAdd support for Internet Storage options (RFC4174)There's an RFC 4174 that we don't seem to support. One day we should. This is filed for completeness. At this time I'm not aware of anyone needing those options.There's an RFC 4174 that we don't seem to support. One day we should. This is filed for completeness. At this time I'm not aware of anyone needing those options.outstandinghttps://gitlab.isc.org/isc-projects/bind9/-/issues/2231error: undefined symbol: _Unwind_Backtrace on OpenBSD 6.82020-11-13T10:25:40ZMichal Nowakerror: undefined symbol: _Unwind_Backtrace on OpenBSD 6.8`v9_11` and `v9_16` (but not `main`) fail to build on OpenBSD 6.8 with Clang 10.0.1 (OpenBSD 6.7 with Clang 8.0.1 seems to be fine):
```
ld: error: undefined symbol: _Unwind_Backtrace
>>> referenced by backtrace.c:120
>>> ...`v9_11` and `v9_16` (but not `main`) fail to build on OpenBSD 6.8 with Clang 10.0.1 (OpenBSD 6.7 with Clang 8.0.1 seems to be fine):
```
ld: error: undefined symbol: _Unwind_Backtrace
>>> referenced by backtrace.c:120
>>> backtrace.o:(isc_backtrace_gettrace) in archive ../isc/libisc.a
ld: error: undefined symbol: _Unwind_GetIP
>>> referenced by backtrace.c:101
>>> backtrace.o:(btcallback) in archive ../isc/libisc.a
clang: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error 1 in target 'sample-request'
ld: error: undefined symbol: _Unwind_Backtrace
>>> referenced by backtrace.c:120
>>> backtrace.o:(isc_backtrace_gettrace) in archive ../isc/libisc.a
ld: error: undefined symbol: _Unwind_GetIP
>>> referenced by backtrace.c:101
>>> backtrace.o:(btcallback) in archive ../isc/libisc.a
clang: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error 1 in target 'resolve'
ld: error: undefined symbol: _Unwind_Backtrace
>>> referenced by backtrace.c:120
>>> backtrace.o:(isc_backtrace_gettrace) in archive ../isc/libisc.a
ld: error: undefined symbol: _Unwind_GetIP
>>> referenced by backtrace.c:101
>>> backtrace.o:(btcallback) in archive ../isc/libisc.a
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
Configuring with `--disable-backtrace` makes the build pass.November 2020 (9.11.25, 9.11.25-S1, 9.16.9, 9.16.9-S1, 9.17.7)Michał KępieńMichał Kępieńhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2230legacy system test fails intermittently2020-11-13T11:17:19ZMark Andrewslegacy system test fails intermittentlyJob [#1241880](https://gitlab.isc.org/isc-projects/bind9/-/jobs/1241880) failed for 4f4a728dee3253d628f15e2bd902c88b69d1dd64:
```
I:legacy:checking recursive lookup to edns 512 server fails (16)
7549I:legacy:failed
```
The SOA record b...Job [#1241880](https://gitlab.isc.org/isc-projects/bind9/-/jobs/1241880) failed for 4f4a728dee3253d628f15e2bd902c88b69d1dd64:
```
I:legacy:checking recursive lookup to edns 512 server fails (16)
7549I:legacy:failed
```
The SOA record being queried for is learnt via the AAAA response over TCP due to the UDP response setting tc=1.November 2020 (9.11.25, 9.11.25-S1, 9.16.9, 9.16.9-S1, 9.17.7)Mark AndrewsMark Andrewshttps://gitlab.isc.org/isc-projects/bind9/-/issues/2229Private file is temporarily invalid.2020-10-23T08:57:42ZMark AndrewsPrivate file is temporarily invalid.Job [#1237357](https://gitlab.isc.org/isc-projects/bind9/-/jobs/1237357) failed for 6f89451d3ee3e466993f999c4b2e7802000cc0b4:
```
I:kasp:error: missing CDS record in response for key 46399
8327I:kasp:error: CDS RRset not signed with key...Job [#1237357](https://gitlab.isc.org/isc-projects/bind9/-/jobs/1237357) failed for 6f89451d3ee3e466993f999c4b2e7802000cc0b4:
```
I:kasp:error: missing CDS record in response for key 46399
8327I:kasp:error: CDS RRset not signed with key 46399
8328I:kasp:error: missing CDNSKEY record in response for key 46399
8329I:kasp:error: CDNSKEY RRset not signed with key 46399
8330I:kasp:failed
```
```
22-Oct-2020 05:36:49.245 keymgr: examine KSK view-rsasha256.kasp/RSASHA256/46399 type DNSKEY in state OMNIPRESENT
22-Oct-2020 05:36:49.245 keymgr: KSK view-rsasha256.kasp/RSASHA256/46399 type DNSKEY in stable state OMNIPRESENT
22-Oct-2020 05:36:49.245 keymgr: examine KSK view-rsasha256.kasp/RSASHA256/46399 type KRRSIG in state OMNIPRESENT
22-Oct-2020 05:36:49.245 keymgr: KSK view-rsasha256.kasp/RSASHA256/46399 type KRRSIG in stable state OMNIPRESENT
22-Oct-2020 05:36:49.245 keymgr: examine KSK view-rsasha256.kasp/RSASHA256/46399 type DS in state OMNIPRESENT
22-Oct-2020 05:36:49.245 keymgr: KSK view-rsasha256.kasp/RSASHA256/46399 type DS in stable state OMNIPRESENT
22-Oct-2020 05:36:49.245 dns_dnssec_findzonekeys2: error reading ./Kview-rsasha256.kasp.+008+46399.private: end of file
22-Oct-2020 05:36:49.245 Fetching view-rsasha256.kasp/RSASHA256/6429 (ZSK) from key repository.
22-Oct-2020 05:36:49.245 zone view-rsasha256.kasp/IN/external-view (signed): sign_apex:dns__zone_findkeys -> end of file
22-Oct-2020 05:36:49.245 DNSKEY view-rsasha256.kasp/RSASHA256/6429 (ZSK) is now published
22-Oct-2020 05:36:49.245 zone_settimer: zone view-rsasha256.kasp/IN/external-view (signed): enter
22-Oct-2020 05:36:49.245 CDS for key view-rsasha256.kasp/RSASHA256/46399 is now published
22-Oct-2020 05:36:49.245 CDNSKEY for key view-rsasha256.kasp/RSASHA256/46399 is now published
22-Oct-2020 05:36:49.245 zone_journal: zone view-rsasha256.kasp/IN/internal-view (signed): enter
```https://gitlab.isc.org/isc-projects/bind9/-/issues/2228make depend fails with gcc: error: dnstap.pb-c.c: No such file or directory2020-11-04T21:22:11ZMichal Nowakmake depend fails with gcc: error: dnstap.pb-c.c: No such file or directoryOn `v9_11` `make depend` [prints](https://gitlab.isc.org/isc-projects/bind9/-/jobs/1236814/raw):
```
$ make depend >/dev/null
gcc: error: dnstap.pb-c.c: No such file or directory
dnstap-read.c:51:10: fatal error: dns/dnstap.pb-c.h: No su...On `v9_11` `make depend` [prints](https://gitlab.isc.org/isc-projects/bind9/-/jobs/1236814/raw):
```
$ make depend >/dev/null
gcc: error: dnstap.pb-c.c: No such file or directory
dnstap-read.c:51:10: fatal error: dns/dnstap.pb-c.h: No such file or directory
51 | #include <dns/dnstap.pb-c.h>
| ^~~~~~~~~~~~~~~~~~~
compilation terminated.
```
On `v9_11` and `v9_16` the command `make depend | grep "error:" && exit 1` from `.gitlab-ci.yml` won't work because the these errors go to stderr and we look for then on stdin. `make depend 2>&1 | grep "error:" && exit 1` should do.November 2020 (9.11.25, 9.11.25-S1, 9.16.9, 9.16.9-S1, 9.17.7)https://gitlab.isc.org/isc-projects/stork/-/issues/435ui system tests needs to be adapted to latest changes on master2021-02-23T07:56:50ZMichal Nowikowskiui system tests needs to be adapted to latest changes on masterNow they are broken as testing framework for containers has been changed.Now they are broken as testing framework for containers has been changed.0.14Wlodzimierz WencelWlodzimierz Wencel