Bug 491722
| Summary: | Installing Rawhide (clearpart --linux) on top of RAID1 formatted system fails | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | anaconda-maint-list, jlaska, jturner, pjones, rmaximo, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-04-02 13:56:10 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: | 446452 | ||
| Attachments: | |||
Created attachment 336341 [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 raid1 storage, then installing rawhide. First install raid1 (release noted below), then clearpart rawhide GUEST TEST FROM TO RESULT ================================================================= vguest1 clearpart --linux RHEL-4-U7 rawhide FAIL (bug#491722) vguest2 clearpart --linux RHEL-5-Server-U3 rawhide FAIL (bug#491722) vguest3 clearpart --linux F-10-GOLD rawhide FAIL (bug#491722) vguest4 clearpart --linux F-9-GOLD rawhide FAIL (bug#491722) One a system that hits this failure ... sh-4.0# cat /proc/mdstat Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] [linear] unused devices: <none> Created attachment 336344 [details]
Attached traceback automatically from anaconda.
Created attachment 336346 [details]
Attached traceback automatically from anaconda.
Created attachment 336348 [details]
Attached traceback automatically from anaconda.
*** This bug has been marked as a duplicate of bug 491754 *** Created attachment 339521 [details]
Attached traceback automatically from anaconda.
|
The following was filed automatically by anaconda: anaconda 11.5.0.35 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devices.py", line 800, in commit raise DeviceError("cannot commit to disk %s after %d attempts" % (self.name, maxTries,)) File "/usr/lib/anaconda/storage/devices.py", line 1130, in create self.disk.commit() File "/usr/lib/anaconda/storage/deviceaction.py", line 206, in execute self.device.create(intf=intf) 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() DeviceError: cannot commit to disk vda after 5 attempts