ISC Open Source Projects issueshttps://gitlab.isc.org/groups/isc-projects/-/issues2024-02-28T12:06:07Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/3007Kea builds are not reproducible2024-02-28T12:06:07ZSudip MukherjeeKea builds are not reproducible---
name: Bug report
about: The latest version of kea is failing the reproducible build as it adds the build path in kea-admin script.
---
**Describe the bug**
The latest version of kea is failing the reproducible build as it adds the ...---
name: Bug report
about: The latest version of kea is failing the reproducible build as it adds the build path in kea-admin script.
---
**Describe the bug**
The latest version of kea is failing the reproducible build as it adds the build path in kea-admin script.
**To Reproduce**
Steps to reproduce the behavior:
1. Build kea
2. Again build kea at a different build location
3. Use diffoscope to compare kea-admin
4. See error
The result can be seen at https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230806-_h282f1z/packages/diff-html/
**Expected behavior**
The built kea-admin should not contain any reference to build path.
**Environment:**
- Kea version: v2.5.0
- OS: All
- Which features were compiled in (in particular which backends): NA
- If/which hooks where loaded in: NA
**Additional Information**
The attached patch will fix the reproducible build and verified with diffoscope. [0001-kea-fix-reproducible-build-failure.patch](/uploads/7b4b13a72d4953a65e6768bdc4f78483/0001-kea-fix-reproducible-build-failure.patch)
**Contacting you**
Please email at sudipm.mukherjee@gmail.comoutstandinghttps://gitlab.isc.org/isc-projects/bind9/-/issues/4248gcc sid amd64 failing all tests post provider merge2023-09-04T09:26:47ZMark Andrewsgcc sid amd64 failing all tests post provider mergeJob [#3574327](https://gitlab.isc.org/isc-projects/bind9/-/jobs/3574327) failed for 9c83c0cb3c78957c458601dabe37d106e43812ff:Job [#3574327](https://gitlab.isc.org/isc-projects/bind9/-/jobs/3574327) failed for 9c83c0cb3c78957c458601dabe37d106e43812ff:September 2023 (9.16.44, 9.16.44-S1, 9.18.19, 9.18.19-S1, 9.19.17)https://gitlab.isc.org/isc-projects/bind9/-/issues/4247Autosign resigning too fast after dnssec-settime calls2024-03-21T15:29:09ZMark AndrewsAutosign resigning too fast after dnssec-settime callsJob [#3570991](https://gitlab.isc.org/isc-projects/bind9/-/jobs/3570991) failed for ce1db0017ee498c3c9e0d632b83113a344d25dda:
I've seen autosign fail in the ZSK roll test several times and it appears to be because dnssec-signzone is bei...Job [#3570991](https://gitlab.isc.org/isc-projects/bind9/-/jobs/3570991) failed for ce1db0017ee498c3c9e0d632b83113a344d25dda:
I've seen autosign fail in the ZSK roll test several times and it appears to be because dnssec-signzone is being called in the same second as dnssec-settime. dnssec-signzone uses the phase `is set and is in the past` as the determinant of when things change. Should this be made `is set and is now or in the past`? Which behaviour is consistent with named's behaviour? Which behaviour is less error prone? If we don't change the behaviour we need to add sleeps to ensure the tests succeed.
```
-S This option enables smart signing, which instructs dnssec-signzone to search the key repository for keys that match the zone
being signed, and to include them in the zone if appropriate.
When a key is found, its timing metadata is examined to determine how it should be used, according to the following rules.
Each successive rule takes priority over the prior ones:
If no timing metadata has been set for the key, the key is published in the zone and used to sign the zone.
If the key's publication date is set and is in the past, the key is published in the zone.
If the key's activation date is set and is in the past, the key is published (regardless of publication date) and used to
sign the zone.
If the key's revocation date is set and is in the past, and the key is published, then the key is revoked, and the revoked
key is used to sign the zone.
If either the key's unpublication or deletion date is set and in the past, the key is NOT published or used to sign the
zone, regardless of any other metadata.
If the key's sync publication date is set and is in the past, synchronization records (type CDS and/or CDNSKEY) are
created.
If the key's sync deletion date is set and is in the past, synchronization records (type CDS and/or CDNSKEY) are removed.
```
```
2023-08-08 00:59:52 INFO:autosign I:autosign_tmp_x_6wkr8z:preparing ZSK roll
2023-08-08 00:59:52 INFO:autosign I:autosign_tmp_x_6wkr8z:ns1 A zone reload and thaw was started.
2023-08-08 00:59:52 INFO:autosign I:autosign_tmp_x_6wkr8z:ns1 Check the logs to see the result.
2023-08-08 00:59:56 INFO:autosign I:autosign_tmp_x_6wkr8z:revoking key to duplicated key ID
2023-08-08 00:59:56 INFO:autosign dnssec-settime: warning: Permissions on the file ns2/Kbar.+013+59973.private have changed from 0644 to 0600 as a result of this operation.
2023-08-08 00:59:56 INFO:autosign I:autosign_tmp_x_6wkr8z:ns2 A zone reload and thaw was started.
2023-08-08 00:59:56 INFO:autosign I:autosign_tmp_x_6wkr8z:ns2 Check the logs to see the result.
2023-08-08 00:59:56 INFO:autosign I:autosign_tmp_x_6wkr8z:waiting for changes to take effect
2023-08-08 01:00:01 INFO:autosign I:autosign_tmp_x_6wkr8z:checking former standby key 5259 is now active (53)
2023-08-08 01:00:01 INFO:autosign I:autosign_tmp_x_6wkr8z:failed
```
```
echo_i "preparing ZSK roll"
starttime=$($PERL -e 'print time(), "\n";')
oldfile=$(cat active.key)
oldid=$(keyfile_to_key_id "$(cat active.key)")
newfile=$(cat standby.key)
newid=$(keyfile_to_key_id "$(cat standby.key)")
$SETTIME -K ns1 -I now -D now+25 $oldfile > settime.out.test$n.1 || ret=1
$SETTIME -K ns1 -i 0 -S $oldfile $newfile > settime.out.test$n.2 || ret=1
# note previous zone serial number
oldserial=$($DIG $DIGOPTS +short soa . @10.53.0.1 | awk '{print $3}')
($RNDCCMD 10.53.0.1 freeze . 2>&1 | sed 's/^/ns1 /' | cat_i) || ret=1
cp ns1/root.db.signed ns1/root.db.1
$SIGNER -S -o . -O full -K ns1 -f ns1/root.db.signed ns1/root.db.1 > signing.root.out$n 2>&1 || ret=1
($RNDCCMD 10.53.0.1 thaw . 2>&1 | sed 's/^/ns1 /' | cat_i) || ret=1
sleep 4
echo_i "revoking key to duplicated key ID"
$SETTIME -R now -K ns2 Kbar.+013+59973.key > settime.out.test$n.3 || ret=1
($RNDCCMD 10.53.0.2 freeze bar. 2>&1 | sed 's/^/ns2 /' | cat_i) || ret=1
cp ns2/bar.db.signed ns2/bar.db
$SIGNER -S -o bar. -O full -K ns2 ns2/bar.db > signing.bar.out$n 2>&1 || ret=1
($RNDCCMD 10.53.0.2 thaw bar. 2>&1 | sed 's/^/ns2 /' | cat_i) || ret=1
echo_i "waiting for changes to take effect"
sleep 5
echo_i "checking former standby key $newid is now active ($n)"
ret=0
$DIG $DIGOPTS dnskey . @10.53.0.1 > dig.out.ns1.test$n || ret=1
grep 'RRSIG.*'" $newid "'\. ' dig.out.ns1.test$n > /dev/null || ret=1
n=$((n + 1))
if [ $ret != 0 ]; then echo_i "failed"; fi
status=$((status + ret))
```
```
08-Aug-2023 00:59:52.469 allocate new control connection
08-Aug-2023 00:59:52.469 received control channel command 'freeze .'
08-Aug-2023 00:59:52.469 loop exclusive mode: starting
08-Aug-2023 00:59:52.469 loop exclusive mode: started
08-Aug-2023 00:59:52.469 zone_dump: zone ./IN: enter
08-Aug-2023 00:59:52.469 loop exclusive mode: ending
08-Aug-2023 00:59:52.469 loop exclusive mode: ended
08-Aug-2023 00:59:52.469 freezing zone './IN': success
08-Aug-2023 00:59:52.469 freeing control connection
08-Aug-2023 00:59:52.497 dump_done: zone ./IN: enter
08-Aug-2023 00:59:52.497 zone_journal_compact: zone ./IN: target journal size 7662
08-Aug-2023 00:59:52.497 zone ./IN: dns_journal_compact: success
08-Aug-2023 00:59:52.509 allocate new control connection
08-Aug-2023 00:59:52.509 received control channel command 'thaw .'
08-Aug-2023 00:59:52.509 loop exclusive mode: starting
08-Aug-2023 00:59:52.509 loop exclusive mode: started
08-Aug-2023 00:59:52.509 zone ./IN: starting load
08-Aug-2023 00:59:52.509 zone_startload: zone ./IN: enter
08-Aug-2023 00:59:52.509 loop exclusive mode: ending
08-Aug-2023 00:59:52.509 loop exclusive mode: ended
08-Aug-2023 00:59:52.509 thawing zone './IN': success
08-Aug-2023 00:59:52.509 freeing control connection
08-Aug-2023 00:59:52.509 zone_loaddone: zone ./IN: enter
08-Aug-2023 00:59:52.509 zone ./IN: number of nodes in database: 5
08-Aug-2023 00:59:52.509 zone ./IN: loaded; checking validity
08-Aug-2023 00:59:52.509 dns_zone_verifydb: zone ./IN: enter
08-Aug-2023 00:59:52.509 zone ./IN: zone serial (2000042101) unchanged. zone may fail to transfer to secondaries.
08-Aug-2023 00:59:52.509 zone ./IN: replacing zone database
08-Aug-2023 00:59:52.509 calling free_rbtdb(.)
08-Aug-2023 00:59:52.509 done free_rbtdb(.)
08-Aug-2023 00:59:52.509 zone ./IN: loaded serial 2000042101 (DNSSEC signed)
08-Aug-2023 00:59:52.509 zone_postload: zone ./IN: done
08-Aug-2023 00:59:52.509 zone__settimer: zone ./IN: enter
```April 2024 (9.16.50, 9.16.50-S1, 9.18.26, 9.18.26-S1, 9.19.23)https://gitlab.isc.org/isc-projects/kea/-/issues/3006Kea fails to listen alongside dnsmasq, but doesn't report a failure2023-10-25T11:41:34ZZenKea fails to listen alongside dnsmasq, but doesn't report a failureUsing Gentoo with kernel 6.1.41 and net-misc/kea-2.2.0-1::gentoo USE="filecaps openssl samples -debug -doc -mysql -postgres -shell -test" PYTHON_SINGLE_TARGET="python3_11 -python3_10" 0 KiB
Kea starts without an error:
```
kea-dhcp4 -...Using Gentoo with kernel 6.1.41 and net-misc/kea-2.2.0-1::gentoo USE="filecaps openssl samples -debug -doc -mysql -postgres -shell -test" PYTHON_SINGLE_TARGET="python3_11 -python3_10" 0 KiB
Kea starts without an error:
```
kea-dhcp4 -c /etc/kea/kea-dhcp4.conf -d
2023-08-08 10:44:58.401 DEBUG [kea-dhcp4.dhcp4/8231.140323795412096] DHCP4_START_INFO pid: 8231, server port: 67, client port: 0, verbose: yes
2023-08-08 10:44:58.402 INFO [kea-dhcp4.dhcp4/8231.140323795412096] DHCP4_STARTING Kea DHCPv4 server version 2.2.0-gentoo (stable) starting
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.dhcp4/8231.140323795412096] DHCP4_OPEN_SOCKET opening service sockets on port 67
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command list-commands registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command build-report registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command config-backend-pull registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command config-get registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command config-reload registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command config-set registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command config-test registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command config-write registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command dhcp-enable registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command dhcp-disable registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command libreload registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command leases-reclaim registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command server-tag-get registered
2023-08-08 10:44:58.402 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command shutdown registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command status-get registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command version-get registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-get registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-reset registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-remove registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-get-all registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-reset-all registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-remove-all registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-sample-age-set registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-sample-age-set-all registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-sample-count-set registered
2023-08-08 10:44:58.403 DEBUG [kea-dhcp4.commands/8231.140323795412096] COMMAND_REGISTERED Command statistic-sample-count-set-all registered
```
but does not actually listen on any ports. I think it does this when dnsmasq is listening on 0.0.0.0, but I defined both interfaces for it to listen on with:
```
"interfaces": [ "fib.lan/10.10.10.1", "ethernet2/192.168.2.1" ]
```
Stopping dnsmasq (which was started by libvirtd) resolves this, but I was able to run ISC this way.outstandinghttps://gitlab.isc.org/isc-projects/bind9/-/issues/4246use pytest runner to run system tests for out-of-tree tests2023-08-21T14:19:40ZTom Krizekuse pytest runner to run system tests for out-of-tree testsImplement support to run system tests for out of tree builds with the pytest system test runner.
This is one of the last uses of the legacy runner in our CI (along with OpenBSD and CentOS7 on ~"v9.18").
Related #3810Implement support to run system tests for out of tree builds with the pytest system test runner.
This is one of the last uses of the legacy runner in our CI (along with OpenBSD and CentOS7 on ~"v9.18").
Related #3810September 2023 (9.16.44, 9.16.44-S1, 9.18.19, 9.18.19-S1, 9.19.17)Tom KrizekTom Krizekhttps://gitlab.isc.org/isc-projects/kea/-/issues/3005ddns CHG_ADD before CHG_REMOVE2023-11-16T18:46:52Zphilip-smartbitddns CHG_ADD before CHG_REMOVE---
name: ddns add nsupdate before remove nsupdate
---
**Describe the bug**
we updated kea to 2.4.0 and set ddns-update-on-renew to true. Since the update we noticed that some hosts lost their dns records (but had a correct lease). fr...---
name: ddns add nsupdate before remove nsupdate
---
**Describe the bug**
we updated kea to 2.4.0 and set ddns-update-on-renew to true. Since the update we noticed that some hosts lost their dns records (but had a correct lease). from around 13:00 07/aug/2023 until now we had 6 hosts losing their dns record. we updated to kea 2.4.0 on 13:00 07/aug/2023
In the kea ddns log we noticed that the problem hosts all showed a CHG_ADD before a CHG_REMOVE:
2023-08-07 18:07:36.634 INFO [kea-dhcp-ddns.d2-to-dns/1587] DHCP_DDNS_ADD_SUCCEEDED DHCP_DDNS Request ID 000201B0E0B8DAF410D5E089236F7462BDCB78A628FBA03A6D38ADF43A848AF348D3F3: successfully added the DNS mapping addition for this request: Type: 0 (CHG_ADD)
Forward Change: yes
Reverse Change: yes
FQDN: [host01.internal.]
IP Address: [10.20.30.40]
DHCID: [000201B0E0B8DAF410D5E089236F7462BDCB78A628FBA03A6D38ADF43A848AF348D3F3]
Lease Expires On: 20230807161112
Lease Length: 216
Conflict Resolution: no
2023-08-07 18:07:36.674 INFO [kea-dhcp-ddns.d2-to-dns/1587] DHCP_DDNS_REMOVE_SUCCEEDED DHCP_DDNS Request ID 000201B0E0B8DAF410D5E089236F7462BDCB78A628FBA03A6D38ADF43A848AF348D3F3: successfully removed the DNS mapping addition for this request: Type: 1 (CHG_REMOVE)
Forward Change: yes
Reverse Change: yes
FQDN: [host01.internal.]
IP Address: [10.20.30.40]
DHCID: [000201B0E0B8DAF410D5E089236F7462BDCB78A628FBA03A6D38ADF43A848AF348D3F3]
Lease Expires On: 20230807154204
Lease Length: 216
Conflict Resolution: no
**To Reproduce**
Steps to reproduce the behavior:
1. Run Kea dhcp4 with the following settings enabled:
"ddns-update-on-renew": true,
"ddns-use-conflict-resolution": false
2. A few hunderd vm's doing a renew every 1800 seconds
3. wait and randomly some hosts lose their dns record's
4. See error above
**Expected behavior**
we expect that kea ddns *always* does a CHG_REMOVE before a CHG_ADD
**Environment:**
- Kea version: 2.4.0 with default multithreading on, package installed via cloudsmith debian repo
- OS: Debian 11
- ha is enabled with default multithreading on, hot-standby
- auth dns server is powerdns 4.8.1
**Additional Information**
we only use dhcp4, no dhcp6
we configured powerdns with distributor-threads=1 and reuseport=no
The kea and (power)dns vm's didn't have high cpu usage or iowait, they weren't overload in any way.
**Contacting you**
contact via gitlab or emailnext-stable-2.6https://gitlab.isc.org/isc-projects/stork/-/issues/1137Alpine Setup script not available2023-09-28T11:20:25ZThomas GerstenbergAlpine Setup script not availableStork documentation chapter [2.5.1.3](https://stork.readthedocs.io/en/latest/install.html#installing-on-alpine) mentions a setup script to install stork on Alpine ([https://dl.cloudsmith.io/public/isc/stork/cfg/setup/setup.alpine.sh](htt...Stork documentation chapter [2.5.1.3](https://stork.readthedocs.io/en/latest/install.html#installing-on-alpine) mentions a setup script to install stork on Alpine ([https://dl.cloudsmith.io/public/isc/stork/cfg/setup/setup.alpine.sh](https://dl.cloudsmith.io/public/isc/stork/cfg/setup/setup.alpine.sh)).
This script however is not available on cloudsmith.
I can imagine that this is related to #863. However, if there are no packages available, the documentation should not state that there are.1.13Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/keama/-/issues/32keama should use // comments in generated configs, not #2023-09-21T07:42:23ZTomek Mrugalskikeama should use // comments in generated configs, not #While both are accepted by Kea, the double slash comments are better for handling the JSON files.
Yes, the JSON standard doesn't allow comments, but the files could be interpreted as javascript files
and then many editors will understand...While both are accepted by Kea, the double slash comments are better for handling the JSON files.
Yes, the JSON standard doesn't allow comments, but the files could be interpreted as javascript files
and then many editors will understand the syntax. This is convenient for example when importing
the snippets into Sphinx or viewing the files with VSCode.4.5.1https://gitlab.isc.org/isc-projects/bind9/-/issues/4245Incorrect return values in rpz's addr and drop functions2023-08-31T15:03:41ZMark AndrewsIncorrect return values in rpz's addr and drop functions`addr` and `drop` should `return 0` after calling `setret` rather than `return 1` as the error has already been logged. This is fallout from the `set -e` changes.`addr` and `drop` should `return 0` after calling `setret` rather than `return 1` as the error has already been logged. This is fallout from the `set -e` changes.September 2023 (9.16.44, 9.16.44-S1, 9.18.19, 9.18.19-S1, 9.19.17)https://gitlab.isc.org/isc-projects/bind9/-/issues/4244dnssec-signzone should ensure the modification time changes2023-08-09T12:39:56ZMark Andrewsdnssec-signzone should ensure the modification time changesWhen re-signing a zone dnssec-signzone should ensure that the modification time of the signed zone increments. If dnssec-signzone is called too quickly in succession the modification time may not change which can lead to the zone not be...When re-signing a zone dnssec-signzone should ensure that the modification time of the signed zone increments. If dnssec-signzone is called too quickly in succession the modification time may not change which can lead to the zone not being loaded.September 2023 (9.16.44, 9.16.44-S1, 9.18.19, 9.18.19-S1, 9.19.17)https://gitlab.isc.org/isc-projects/bind9/-/issues/4243_wait_for_stats errors not detected in ixfr system test2023-08-08T00:43:48ZMark Andrews_wait_for_stats errors not detected in ixfr system testSeptember 2023 (9.16.44, 9.16.44-S1, 9.18.19, 9.18.19-S1, 9.19.17)Mark AndrewsMark Andrewshttps://gitlab.isc.org/isc-projects/kea/-/issues/3004Replace output_options by output-options2023-09-18T08:15:59ZFrancis DupontReplace output_options by output-optionsThe keyword `output_options` is the only keyword in server and agent syntaxes with the underscore `_` character. The idea is after making `output-options` an alias (#3003) to swap them i.e. to make the dash `-` variant the main one.The keyword `output_options` is the only keyword in server and agent syntaxes with the underscore `_` character. The idea is after making `output-options` an alias (#3003) to swap them i.e. to make the dash `-` variant the main one.kea2.5.2Razvan BecheriuRazvan Becheriuhttps://gitlab.isc.org/isc-projects/kea/-/issues/3003Add output-options as alias of output_options2023-09-18T08:08:08ZFrancis DupontAdd output-options as alias of output_options`output_options` is the only syntax entry using `_` vs `-`: as explained in https://gitlab.isc.org/isc-projects/kea/-/issues/2904#note_379090 we can easily make `output-options` an alias of `output_options` in flex (.ll) files.`output_options` is the only syntax entry using `_` vs `-`: as explained in https://gitlab.isc.org/isc-projects/kea/-/issues/2904#note_379090 we can easily make `output-options` an alias of `output_options` in flex (.ll) files.kea2.5.1Francis DupontFrancis Duponthttps://gitlab.isc.org/isc-projects/kea/-/issues/3002Missing examples for Secure Zero Touch Provisioning options2023-09-21T07:39:15ZPiotrek ZadrogaMissing examples for Secure Zero Touch Provisioning optionsThere are no examples of usage of SZTP options in `doc/examples`:
* DHCPv4 Option code \#143
* DHCPv6 Option code \#136.There are no examples of usage of SZTP options in `doc/examples`:
* DHCPv4 Option code \#143
* DHCPv6 Option code \#136.kea2.5.2Piotrek ZadrogaPiotrek Zadrogahttps://gitlab.isc.org/isc-projects/dhcp/-/issues/290The timer of dhclient doesn't work if date changed2023-08-30T12:51:28Zqianfan ZhaoThe timer of dhclient doesn't work if date changedHi:
dhclient use `gettimeofday(&cur_tv, NULL);` get current time and use this wall time as timer resource. So the timer resource is not valid when the date is changed.
Next is the dhclient logs when no cable plugged in:
```
Jan 9 07...Hi:
dhclient use `gettimeofday(&cur_tv, NULL);` get current time and use this wall time as timer resource. So the timer resource is not valid when the date is changed.
Next is the dhclient logs when no cable plugged in:
```
Jan 9 07:31:48 buildroot daemon.info dhclient: Internet Systems Consortium DHCP Client 4.4.3
Jan 9 07:31:48 buildroot daemon.info dhclient: Copyright 2004-2022 Internet Systems Consortium.
Jan 9 07:31:48 buildroot daemon.info dhclient: All rights reserved.
Jan 9 07:31:48 buildroot daemon.info dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jan 9 07:31:48 buildroot daemon.info dhclient:
Jan 9 07:31:49 buildroot daemon.info dhclient: Listening on LPF/FE0/0c:fe:5d:42:5d:eb
Jan 9 07:31:49 buildroot daemon.info dhclient: Sending on LPF/FE0/0c:fe:5d:42:5d:eb
Jan 9 07:31:49 buildroot daemon.info dhclient: Sending on Socket/fallback
Jan 9 07:31:49 buildroot daemon.info dhclient: DHCPDISCOVER on FE0 to 255.255.255.255 port 67 interval 4
Jan 9 07:31:53 buildroot daemon.info dhclient: DHCPDISCOVER on FE0 to 255.255.255.255 port 67 interval 4
Jan 9 07:31:57 buildroot daemon.info dhclient: DHCPDISCOVER on FE0 to 255.255.255.255 port 67 interval 6
Jan 9 07:32:03 buildroot daemon.info dhclient: DHCPDISCOVER on FE0 to 255.255.255.255 port 67 interval 14
<date is changed after this>
```
It should print sometings like this and try again later:
```
dhclient: No DHCPOFFERS received.
dhclient: No working leases in persistent database - sleeping.
```
But after the date changed, dhclient hangup forever.https://gitlab.isc.org/isc-projects/stork/-/issues/1136API mock has invalid filename2023-09-15T07:41:27ZSlawek FigielAPI mock has invalid filenameThe issue was found by @slawek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393232).
The build system generates the `api_mock.go` file instead of `apimock_test.go`. The old name was reverted b...The issue was found by @slawek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393232).
The build system generates the `api_mock.go` file instead of `apimock_test.go`. The old name was reverted by [this commit](https://gitlab.isc.org/isc-projects/stork/-/commit/9b140db674124d2a0ca3bc96420c9b2317e719d5).1.13Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1135Not summarized shared network statistic counters2023-10-04T10:04:48ZSlawek FigielNot summarized shared network statistic countersThe issue was found by @slawek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393204).
The shared network statistics are not summarized.
I've generated traffic for the `192.1.16.0/24` subnet in...The issue was found by @slawek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393204).
The shared network statistics are not summarized.
I've generated traffic for the `192.1.16.0/24` subnet in the `mouse` shared network.
The pie chart shows some addresses are assigned, but the counters below show zero values.
![image](https://gitlab.isc.org/isc-projects/stork/uploads/dd62de7153437f7aad8fd682de511acd/image.png)
The subnet page displays a proper pie chart and counter values.
![image](https://gitlab.isc.org/isc-projects/stork/uploads/fe6be2d9d0ea064b61b77089371c2816/image.png)1.13Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1134Host filtration returns unexpected results2023-08-22T13:39:07ZSlawek FigielHost filtration returns unexpected resultsThe issue was found by @slawek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393202).
The subnet list displays unexpected items if the filter value is `128`.
![image](https://gitlab.isc.org/is...The issue was found by @slawek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393202).
The subnet list displays unexpected items if the filter value is `128`.
![image](https://gitlab.isc.org/isc-projects/stork/uploads/2e72740db71b46904797ac409b54b856/image.png)backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/1133Hyperlinks for shared networks on the dashboard2023-09-20T17:22:56ZSlawek FigielHyperlinks for shared networks on the dashboardThe issue was found by @wlodek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393193).
In the dashboard v6 shared networks are not hyperlinks:
![Screenshot_2023-08-02_at_15.29.50](https://gitla...The issue was found by @wlodek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393193).
In the dashboard v6 shared networks are not hyperlinks:
![Screenshot_2023-08-02_at_15.29.50](https://gitlab.isc.org/isc-projects/stork/uploads/1cd7972c3b3e3af8049e6f625bcf7534/Screenshot_2023-08-02_at_15.29.50.png)1.13Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/1132Reset pagination on filter change in config review panel2023-12-12T12:42:20ZSlawek FigielReset pagination on filter change in config review panelThe issue was found by @slawek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393179).
The pagination in the config review panel is not reset when the filters change.
Steps to reproduce:
1. Ch...The issue was found by @slawek during [1.12 sanity checks](https://gitlab.isc.org/isc-projects/stork/-/issues/1124#note_393179).
The pagination in the config review panel is not reset when the filters change.
Steps to reproduce:
1. Choose a daemon with more than 5 enabled checkers and at least 1 issue found.
1. Disable issue filtration (set the "All reports" option).
1. Go to the last page
1. Enable issue filtration (set the "Issues only" option).
1. Observe there are no issues displayed.
![image](https://gitlab.isc.org/isc-projects/stork/uploads/286a3bfdbf25d4a96eb7d5b21a382919/image.png)backlog