Your message dated Sat, 04 Jul 2026 14:42:58 +0000
with message-id <[email protected]>
and subject line Bug#1011533: fixed in chrony 4.6.1-3+deb13u2
has caused the Debian Bug report #1011533,
regarding chrony: kdevops reboot-limit fails between 50-12,000 reboots
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1011533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011533
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 4.2-2
Severity: important
Tags: patch
X-Debbugs-Cc: [email protected]

Dear Maintainer,

When using the new kdevops [0] reboot-limit [1] test to see how may reboots
can happen with debian-testing without a failure I ran have ran 3 tests
with different kernels with the following observations. The point of the
test is to simply instantiate vagrant debian-testing guests, and then
reboot them and detect with ansible if ssh access to the guest is
possible. The test fails upon an ssh timeout or crash. In the list below
a + indicates the test is still running. A single digit expresses how many
times reboots completed successfully.

kernel         | reboots     | with-fix
-------------------------------------------------------------------------       
                                                                                
                           
v5.10.105      | 500         | not-tested-yet
v5.17-rc7      | 1,200       | 2,000+
5.17.0-1-amd64 | 3,300+      | first-run-stil-running

Upon inspection on the failed boots on v5.10.105 and v5.17-rc7 I
noticed the following on both systems:

root@rebootlimit ~ # sudo systemctl list-units --failed
  UNIT              LOAD   ACTIVE SUB    DESCRIPTION                            
                                                                                
                              
    ● [email protected] loaded failed failed ifup for eth0 

I can see then (scraped from a console, sorry about formatting):

]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3                   
                                                                                
                              
]: DHCPOFFER of 192.168.121.240 from 192.168.121.1                              
                                                                                
                              
]: DHCPREQUEST for 192.168.121.240 on eth0 to 255.255.255.255 port 67           
                                                                                
                              
]: DHCPACK of 192.168.121.240 from 192.168.121.1                                
                                                                                
                              
]: bound to 192.168.121.240 -- renewal in 1699 seconds.                         
                                                                                
                              
nd to 192.168.121.240 -- renewal in 1699 seconds.                               
                                                                                
                              
-parts: /etc/network/if-up.d/chrony exited with return code 1                   
                                                                                
                              
p: failed to bring up eth0                                                      
                                                                                
                              
[email protected]: Main process exited, code=exited, status=1/FAILURE           
                                                                                
                              
[email protected]: Failed with result 'exit-code'.

The important line is:

May 21 10:58:58 rebootlimit sh[693]: run-parts: /etc/network/if-up.d/chrony 
exixited with return code 1

Using $(virsh net-dhcp-leases vagrant-libvirt) I see no takers of the IP
address and so there has not been clashes. So my next best guesss given
the lack of output from chrony is that this is a race on bootup.

I'm still testing things but the following adjustment seems to have
helped so far.

--- /etc/network/if-up.d/chrony.old     2022-05-24 16:40:53.112439882 +0000
+++ /etc/network/if-up.d/chrony 2022-05-24 16:41:23.452471796 +0000
@@ -5,6 +5,7 @@
 [ -x /usr/sbin/chronyd ] || exit 0
 
 if [ -e /run/chrony/chronyd.pid ]; then
+    systemctl is-system-running --wait
     chronyc onoffline > /dev/null 2>&1
 fi
 

[0] https://github.com/linux-kdevops/kdevops
[1] 
https://github.com/linux-kdevops/kdevops/blob/master/workflows/demos/reboot-limit/Kconfig

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.105 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chrony depends on:
ii  adduser              3.121
ii  init-system-helpers  1.62
ii  iproute2             5.17.0-2
ii  libc6                2.33-7
ii  libcap2              1:2.44-1
ii  libedit2             3.1-20210910-1
ii  libgnutls30          3.7.4-2
ii  libnettle8           3.7.3-1
ii  libseccomp2          2.5.4-1
ii  tzdata               2022a-1
ii  ucf                  3.0043

chrony recommends no packages.

Versions of packages chrony suggests:
ii  bind9-dnsutils [dnsutils]  1:9.18.1-1
pn  networkd-dispatcher        <none>

-- Configuration Files:
/etc/network/if-up.d/chrony changed:
set -e
[ -x /usr/sbin/chronyd ] || exit 0
if [ -e /run/chrony/chronyd.pid ]; then
    systemctl is-system-running --wait
    chronyc onoffline > /dev/null 2>&1
fi
exit 0


-- no debconf information
--- /etc/network/if-up.d/chrony.old     2022-05-24 16:40:53.112439882 +0000
+++ /etc/network/if-up.d/chrony 2022-05-24 16:41:23.452471796 +0000
@@ -5,6 +5,7 @@
 [ -x /usr/sbin/chronyd ] || exit 0
 
 if [ -e /run/chrony/chronyd.pid ]; then
+    systemctl is-system-running --wait
     chronyc onoffline > /dev/null 2>&1
 fi
 

--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 4.6.1-3+deb13u2
Done: Vincent Blut <[email protected]>

We believe that the bug you reported is fixed in the latest version of
chrony, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Blut <[email protected]> (supplier of updated chrony package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 24 Jun 2026 20:05:59 +0200
Source: chrony
Architecture: source
Version: 4.6.1-3+deb13u2
Distribution: trixie
Urgency: medium
Maintainer: Vincent Blut <[email protected]>
Changed-By: Vincent Blut <[email protected]>
Closes: 1011533
Changes:
 chrony (4.6.1-3+deb13u2) trixie; urgency=medium
 .
   * debian/chrony.if-{post-down,up}:
     - Adjust the if-up and if-down hook scripts so that they always exit
     successfully. (Closes: #1011533)
Checksums-Sha1:
 dc3dd7aeb3742667513c0bb70b414df1e41898a5 2898 chrony_4.6.1-3+deb13u2.dsc
 37b81456263fb4eba16926116a8387a72103bfb4 44356 
chrony_4.6.1-3+deb13u2.debian.tar.xz
 871f53b90ef52875fb8d7586c3f7e1d16b09d669 1382552 
chrony_4.6.1-3+deb13u2.git.tar.xz
 3d9e63e4ef1c9bc84d974dd2a0984f59c255fd94 17532 
chrony_4.6.1-3+deb13u2_source.buildinfo
Checksums-Sha256:
 0336767d54cc761119ba2ada1a5c5e953b4286444aefaf6e6eea13d01a9ae78f 2898 
chrony_4.6.1-3+deb13u2.dsc
 a906229f205efdd69032485d8527843f0bd3018351b3f58b133dee56d0c47af9 44356 
chrony_4.6.1-3+deb13u2.debian.tar.xz
 55309dff267e0c278acd98386d102b3bc2c9bd87af325fe90ed7154f078acc15 1382552 
chrony_4.6.1-3+deb13u2.git.tar.xz
 4a4a7f063b582f9104e850ca47065492eb3b2c0a4bc5074a3ca833f0c4756087 17532 
chrony_4.6.1-3+deb13u2_source.buildinfo
Files:
 b759d41fd84da64f10ef05bc513b9fc9 2898 net optional chrony_4.6.1-3+deb13u2.dsc
 5e3ddfd53d1f617ec703be8f5f9c2bde 44356 net optional 
chrony_4.6.1-3+deb13u2.debian.tar.xz
 91c992ee152a1c8d39ee6b4d54ded5f6 1382552 net optional 
chrony_4.6.1-3+deb13u2.git.tar.xz
 9bae88555fb0a7bba7a23660686cc379 17532 net optional 
chrony_4.6.1-3+deb13u2_source.buildinfo
Git-Tag-Info: tag=0d32b72cd99ecfc5f9584806f99e3c70e2a45891 
fp=1b939355ac4c35cadfbd739c06a328e00c6ace15
Git-Tag-Tagger: Paul Gevers <[email protected]>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmpIsnEACgkQYG0ITkaD
wHmiNg//f+oTur8hHy0lcjXisgazY813RNqTl6wUcCvQRdEl/nqWebZhQMRYfM5P
Xg3aD/QDq8grh8RL/In84A+DPpRbYyP+Ge8gpdQdcZUybZXqYgoUVlUoo7KGu1zF
am1pI1wi6Hy49WwRWCfUdLl9yLg8HBVZEuSiij8ZYywb8ltddqTYGcSK5141Hpnz
RCWttv8aAl15UrBPMH5ulbsjzsWCjNOKGWtWMxHgOccBCx2Z+qYga4Krvy7IkxeI
tMK/STcvS/osTdMHIdUJjywuJFjrxUqLnoXurfs73lIzS5lkQaJP4ibT92NOADtf
D/6b2ivLDC3kbzSURSmEggNl0S0FiIx7m8dcV+P14tfySN3neipEwrCLSZS6bChs
mfZv9tkUJdahhGcdmhlHsA1aJXEDlM7XWS5/zCIR4vpiQI/aOBefeUqUGHp8xHhH
hUbxApj30GyXyR5zw/EOkKDzgXzWuPAOHcjway/iVWzTXit0ueED8fF4cDpn5t1l
q+iiGqNM/+q2mOxk5M1/VzP4fB03OebTHui/Une1f1+Rc870p9lE5Zoy2GTNybvb
SwLYRtv/SNN2+gwTc1jkRkzM8ZpRsc7bqp6sCLV/MFJ6xT2FgRhsCPA7Gw4DZ5lf
4QyBrUEUgkVtW/Nmm8Ca6+OCwaoSUEu+ThwLRKT7R0xl0X/gtYI=
=+MhZ
-----END PGP SIGNATURE-----

Attachment: pgp_vhgMgBjfw.pgp
Description: PGP signature


--- End Message ---

Reply via email to