On Sat, Feb 08, 2025 at 07:35:03PM +0100, Vincent Blut wrote: > Control: merge 1011533 -1 > > Hi, > > The next chrony revision will introduce some changes to the chrony.service > file. Among them, the 'After=network.target' line will be dropped which > I think might help fix this timing issue by letting chronyd start a bit > earlier. > > In the meantime, could you please check wether my assumptions is correct by > modifying chrony.service with the aforementioned line removed. > This can be done by running 'systemctl edit --full chrony.service'. > > Luis, I suspect this issue has the same root cause as the one you > reported in #1011533.ยน It would be nice to know if it can be reproduced > using the 'kdevops reboot-limit' test with the chrony.service file > modified as described above.
+ kdevops list Jeesh, I guess better late than never. That bug report was from 2022. By now we've moved on from vagrant to guestfs and what would make testing on debian even easier is for debian to just get proper debian testing guestfs images out. Can you help us with that? Luis
