Red Hat Bugzilla – Bug 818356
incorrect clock blocks installation
Last modified: 2016-04-26 16:12:18 EDT
Description of problem:
stale hardware clock causes systemd to fsck the read only filesystem in the installer environment
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Set hardware clock outside the fsck window
3.Watch in horror as it tries to fsck a read only filesystem and then dies
I used hwclock to correct the date and it installs fine.
should we take care of this situation? The only Node specific bit I see with this problem is that fsck fails because we've got a ro rootfs.
Do you have a proposed solution? Do we even know if this is still an issue?
(In reply to comment #2)
> Do you have a proposed solution? Do we even know if this is still an issue?
I believe this issue is a generic issue related to fsck - and not to Node.
What I could think of is that fsck / systemd should take care of such a situation.
I've created an upstream bug 947533 to see what they say.
can you still reproduce this with 2.6.0?
I couldn't on a first try.
No response from the reporter and I'm also not able to reproduce it therefor closig this.