Frantisek Sumsal
92631f1962
It looks like the 4 second sleep might not be enough on some slower machines (like the ARM GH Actions nodes) which can lead to the DS RRs propagation to clash with the manual test zone edit, and the signed.test zone then might end up not properly signed: TEST-75-RESOLVED.sh[749]: + : '--- ZONE: signed.test (static DNSSEC) ---' TEST-75-RESOLVED.sh[749]: + run_delv @ns1.unsigned.test signed.test TEST-75-RESOLVED.sh[749]: + run delv -a /etc/bind.keys @ns1.unsigned.test signed.test TEST-75-RESOLVED.sh[778]: + delv -a /etc/bind.keys @ns1.unsigned.test signed.test TEST-75-RESOLVED.sh[779]: + tee /tmp/tmp.2KOIiyrgth TEST-75-RESOLVED.sh[779]: ;; /etc/bind.keys:1: option 'managed-keys' is deprecated TEST-75-RESOLVED.sh[779]: ;; validating signed.test/DS: no valid signature found TEST-75-RESOLVED.sh[779]: ;; validating signed.test/A: no valid signature found TEST-75-RESOLVED.sh[779]: ; unsigned answer TEST-75-RESOLVED.sh[779]: signed.test. 86400 IN A 10.0.0.10 TEST-75-RESOLVED.sh[779]: signed.test. 86400 IN RRSIG A 13 2 86400 20251028114356 20251014101356 39330 signed.test. oo3ca8WPusbBPRhzsEKw3bsBBqFtI8i4bckoMVNzt7lY+udGW6PlaSYj OjpQGgY9oglowVM9bteNtwJKHUbvtw== TEST-75-RESOLVED.sh[749]: + grep -qF '; fully validated' /tmp/tmp.2KOIiyrgth [FAILED] Failed to start TEST-75-RESOLVED.service - TEST-75-RESOLVED. Let's explicitly wait for the DS records propagation to finish before we start editing the test zone to avoid this. I'm still not completely sure if this is the root cause, but it's the best shot I currently have, so I'll let the CIs decide.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS