Bug 491729
| Summary: | Installing Rawhide (clearpart --linux) on top of RAID0 formatted system fails | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> |
| Component: | anaconda | Assignee: | Joel Andres Granados <jgranado> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | bruno, cje, dcantrell, jlaska, jturner, michael.madore, pjones, rmaximo, tcallawa, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | anaconda_trace_hash:42c5e49babe5d154639d16923599f903fdef109f3e6549b3bc221de1d5c76762 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-05-06 21:22:12 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: | |||
| Bug Blocks: | 472555, 495965 | ||
| Attachments: | |||
Created attachment 336356 [details]
Attached traceback automatically from anaconda.
Created attachment 336358 [details]
Attached traceback automatically from anaconda.
Consistently hitting this bug while testing that rawhide can install on top of previous installations. This test matrix focused on installing distros on top of raid0 storage, then installing rawhide. First install raid0 (release noted below), then clearpart rawhide GUEST TEST FROM TO RESULT ================================================================= vguest1 clearpart --linux RHEL-4-U7 rawhide FAIL (bug#491729) vguest2 clearpart --linux RHEL-5-Server-U3 rawhide FAIL (bug#491729) vguest3 clearpart --linux F-10-GOLD rawhide FAIL (bug#491729) vguest4 clearpart --linux F-9-GOLD rawhide FAIL (bug#491729) Created attachment 337035 [details]
Attached traceback automatically from anaconda.
Created attachment 337625 [details]
Attached traceback automatically from anaconda.
*** Bug 492855 has been marked as a duplicate of this bug. *** Created attachment 339589 [details]
Attached traceback automatically from anaconda.
might be stating the obvious but from bug 469466 a workaround is to dd from /dev/zero to initialise the disks. then reboot. not pretty - just in case anyone desperately needs to get past this bug before it's fixed. Created attachment 339825 [details]
The patch that solves the issue.
This error is caused from previous mdadm command failures where the activation of the devices did not fully complete. On my tests, when I included the "--run" argument in the create command, this bug went away.
This patch just went in. It will be present in anaconda version 11.5.0.46. *** Bug 495608 has been marked as a duplicate of this bug. *** |
The following was filed automatically by anaconda: anaconda 11.5.0.35 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/mdraid.py", line 131, in mddestroy raise MDRaidError("mddestroy failed for %s" % device) File "/usr/lib/anaconda/storage/formats/mdraid.py", line 87, in destroy mdraid.mddestroy(self.device) File "/usr/lib/anaconda/storage/deviceaction.py", line 326, in execute self.origFormat.destroy() File "/usr/lib/anaconda/storage/devicetree.py", line 660, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 184, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 115, in turnOnFilesystems anaconda.id.storage.doIt() File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1317, in nextClicked self.anaconda.dispatch.gotoNext() MDRaidError: mddestroy failed for /dev/vda2