[Bug 1172465] New: transactional-update.timer fires immediately at first boot
http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 Bug ID: 1172465 Summary: transactional-update.timer fires immediately at first boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: lnussel@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- openSUSE-MicroOS.armv7l-16.0.0-RaspberryPi2-Snapshot20200528.raw Booted and wondered why systemd-analyze wouldn't show me results. Turns out transactional-update.timer was started immediately at first boot. Maybe related to missing rtc on rpi? So the time warp caused by chrony catching up triggered it? # systemctl status transactional-update.timer * transactional-update.timer - Daily update of the system Loaded: loaded (/usr/lib/systemd/system/transactional-update.timer; enabled; vendor preset: enabled) Active: active (waiting) since Thu 2020-04-23 14:15:38 UTC; 1 months 10 days ago Trigger: Thu 2020-06-04 01:38:53 UTC; 11h left Triggers: * transactional-update.service Docs: man:transactional-update(8) If so why April 23rd rather than end of May when the image was created? # l /var/lib/chrony total 0 drwxr-x--- 1 chrony chrony 0 May 2 22:23 ./ drwxr-xr-x 1 root root 268 Jun 3 13:56 ../ Can and do we want to do something about this behavior or a matter of documentation again? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |armv7 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 http://bugzilla.opensuse.org/show_bug.cgi?id=1172465#c1 --- Comment #1 from Ludwig Nussel <lnussel@suse.com> --- to be more precise, the timer was started of course but also triggered the associated service immediately, ie zypper dup runnning immediately at boot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 http://bugzilla.opensuse.org/show_bug.cgi?id=1172465#c13 --- Comment #13 from Ignaz Forster <iforster@suse.com> ---
From systemd's perspective it did everything correctly. It started the timers and set the triggers when it was asked to do so...
Can I close this as a duplicate of bug #1145193? The alternative would be to add a dependency in transactional-update.timer to chrony-wait.service, but of course I'd prefer to have a more general solution that fixes the underlying problem... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 http://bugzilla.opensuse.org/show_bug.cgi?id=1172465#c14 --- Comment #14 from Ludwig Nussel <lnussel@suse.com> --- no, adding deps to chrony-wait would certainly be wrong. Nevertheless there are still alternatives if we wanted to do something about this. For example forcing the time sync wait in the first boot only. Also, chronyd could be started with the -s option to take the time stamp from the drift file so subsequent boots don't suffer from the same problem -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 http://bugzilla.opensuse.org/show_bug.cgi?id=1172465#c15 --- Comment #15 from Ludwig Nussel <lnussel@suse.com> --- filed bug#1173276 for chrony. that could at least cover reboots -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 http://bugzilla.opensuse.org/show_bug.cgi?id=1172465#c16 Joed L <jlopez777+opensuse@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlopez777+opensuse@gmail.co | |m --- Comment #16 from Joed L <jlopez777+opensuse@gmail.com> --- Can this be closed? Last I heard there is a delay after boot now. ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 http://bugzilla.opensuse.org/show_bug.cgi?id=1172465#c17 --- Comment #17 from Ignaz Forster <iforster@suse.com> --- Meanwhile the transactional-update.timer contains a "Persistent=true" directive, but the problem persists: after a reboot the timer will still be triggered way too early. I assume this would be fixed if bug#1173276 (respectively the Jira ticket linked in there) would be implemented. The (random) delay of up to two hours has been there from the beginning. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com