improve timesyncd epoch on uc20
Bug #1878422 reported by
Ian Johnson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Invalid
|
High
|
Ian Johnson | ||
ubuntu-core-initramfs |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When booting in install mode, and timesyncd clock stamp file is missing we should initialize it to at least as old as the image build.
Ideally from .disk/info file which we don't have at the moment.
When systemd is updated in SRUs we should bump the time-epoch in a reproducible way.
When booting into recover mode, the clock stamp file should be copied up from runmode into recover mode.
Changed in snapd: | |
assignee: | nobody → Ian Johnson (anonymouse67) |
Changed in snapd: | |
milestone: | none → 2.46 |
Changed in snapd: | |
status: | Fix Committed → Fix Released |
Changed in snapd: | |
importance: | Medium → High |
To post a comment you must log in.
No, we do not need fixrtc script.
kernel cmdline must _not_ specify 'fixrtc'
systemd adjusts hardware/kernel clock to be at least when systemd was last released (ie. sometime in 2020). It does that very early during init. And since initrd's init is systemd, the equivalent functionality is already there.
Do you have any symptoms that indicate that above is not working? I.e. do you see system clock coming up as before than 2020? any tls / gpg verification failures (i.e. errors like CA certificate expired, or start date in the future)