Bug 980477
| Summary: | ovirt-firstboot may wipe RHEV Storage Domain if kernel changes device order | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Idith Tal-Kohen <italkohe> |
| Component: | ovirt-node | Assignee: | Mike Burns <mburns> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | abaron, acathrow, bsarathy, cpelland, fdeutsch, gouyang, hadong, hateya, huiwa, italkohe, jboggs, jmoran, leiwang, mburns, ovirt-maint, pep, pm-eus, sgordon, sgrinber, sputhenp, virt-bugs, ycui |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-node-2.5.0-17.el6_4.8 | Doc Type: | Bug Fix |
| Doc Text: |
The kernel ordering of /dev/sdX devices is not necessarily deterministic. When booting the Hypervisor using PXE with the storage_init parameter set to a /dev/sdX device it was therefore possible to accidentally delete data from Red Hat Enterprise Virtualization storage domains.
Additional safe guards have been added to check that the device specified in the storage_init parameter does not contain a storage domain. Installation is blocked where this is the case. To use the storage_init parameter in a deterministic manner specify devices using the paths presented under /dev/mapper/ instead of paths of the form /dev/sdX.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-16 15:29:40 UTC | Type: | --- |
| 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: | 889071 | ||
| Bug Blocks: | |||
|
Description
Idith Tal-Kohen
2013-07-02 13:54:31 UTC
The bug status is MODIFIED, after devel change it to 'ON-QA', we will change it to 'verified' according to comment 15. Change it to 'Verified' according to comment 15. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1077.html |