[Bug 1071763] New: On images meant for systems without a Real Time Clock systemctl-timesyncd should be enabled
http://bugzilla.suse.com/show_bug.cgi?id=1071763 Bug ID: 1071763 Summary: On images meant for systems without a Real Time Clock systemctl-timesyncd should be enabled Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: freek@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- On systems without a Real Time Clock, the system always starts on Jan 1, 1970, which causes problems with files that are created or log entries carrying this date. I learned that the service systemctl-timesyncd preserves clock settings and makes the system start with the last saved time using this service. The enhancement i propose is to enable this service by default in images meant to be used on systems without a RTC. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1071763 http://bugzilla.suse.com/show_bug.cgi?id=1071763#c5 --- Comment #5 from Freek de Kruijf <freek@opensuse.org> --- I just now started with the latest image for the Raspberry Pi 3B, from repository: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp... using image: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2017.12.04-Build4.5.raw.xz I enabled systemd-timesyncd.service also started it, which showed it is active. However after a reboot I do NOT see any change in the date/time until NTP becomes active and the journal shows date/times after each reboot from okt 26 14:29:36, which is apparently the time initrd was build. Looking at the status of systemd-timesyncd.service after the reboot, it is NOT active. This means it is not doing what it is supposed to do. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1071763 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |lnussel@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1071763 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com Component|Basesystem |Patterns Hardware|Other |aarch64 Assignee|lnussel@suse.com |dmueller@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1071763 http://bugzilla.suse.com/show_bug.cgi?id=1071763#c6 matthias sweertvaegher <matthias.sweertvaegher@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.sweertvaegher@gmai | |l.com --- Comment #6 from matthias sweertvaegher <matthias.sweertvaegher@gmail.com> --- any update on this? what is currently the correct way to save datetime between reboots? thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1071763 http://bugzilla.suse.com/show_bug.cgi?id=1071763#c7 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #7 from Tomáš Chvátal <tchvatal@suse.com> --- This is automated batch bugzilla cleanup. The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please feel free to reopen this bug against that version (!you must update the "Version" component in the bug fields, do not just reopen please), or alternatively create a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1071763 http://bugzilla.suse.com/show_bug.cgi?id=1071763#c8 Freek de Kruijf <freek@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Version|Leap 42.3 |Leap 15.1 Resolution|WONTFIX |--- --- Comment #8 from Freek de Kruijf <freek@opensuse.org> --- The system does not start anymore on Jan 1st, 1970, but on the date/time of building the image, however it will start always on that date/time. A better solution would be to have a start date/time in the boot partition which is read at boot time. This date/time should regularly be updated when the system runs and when the system is shutting down. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1071763 Freek de Kruijf <freek@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|On images meant for systems |On images meant for systems |without a Real Time Clock |without a Real Time Clock |systemctl-timesyncd should |systemd-timesyncd should be |be enabled |enabled -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1071763 https://bugzilla.suse.com/show_bug.cgi?id=1071763#c9 --- Comment #9 from Freek de Kruijf <freek@opensuse.org> --- This is still a valid bug report. All Raspberry Pi images I am using still have now chrony as the default time setting utility. They should have systemd-timesyncd as the default. This timesync system sets a system time very early in the boot process at a value which is later than any time the system had before. So no newly created resources will have a date/time before a date/time used earlier in the system. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com