Bug 818356
Summary: | incorrect clock blocks installation | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | luke.varnadore |
Component: | ovirt-node | Assignee: | Fabian Deutsch <fdeutsch> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | acathrow, dyasny, fdeutsch, jboggs, mburns, mgoldboi, ovirt-bugs, ovirt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.7.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-09 11:01:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 947533 | ||
Bug Blocks: |
Description
luke.varnadore
2012-05-02 20:31:02 UTC
Mike, 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. Luke, 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. |