Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 588597
| Summary: | DeviceError: ('device has not been created', 'sdb1') | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> | ||||||
| Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 13 | CC: | anaconda-maint-list, awilliam, dcantrell, jlaska, jonathan, vanmeeuwen+fedora | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | anaconda_trace_hash:baee4239821d5251807ca9c40e06e3e2421e5a57882746e35adf13ba41cc2e76 | ||||||||
| Fixed In Version: | anaconda-13.41-1.fc13 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 592337 (view as bug list) | Environment: | |||||||
| Last Closed: | 2010-05-12 01:03:46 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: | 507681, 592337 | ||||||||
| Attachments: |
|
||||||||
Created attachment 411171 [details]
Attached traceback automatically from anaconda.
I got this when going from a system with two md devices to a default partitioning. Tossing on the blocker list for visibility. Same as bug#568759 ? Looks similar, but without knowing the root cause, hard to tell. This may wind up being fixed by the other issue with md devices getting removed, so I'll wait until that bug is fixed and re-try. for me this is a blocker, per our criteria - any known fail at all when trying to set up a valid partition scheme counts as a blocker. Created attachment 411701 [details]
Attached traceback automatically from anaconda.
Seems this is still happening with 13.40 There is an updates.img available to work around this issue. The updates.img should be applied to anaconda-13.40-1 http://dlehman.fedorapeople.org/updates-588597.img Makes it work here. that would make it fixed in 13.41, right? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers anaconda-13.41-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.41-1.fc13 that makes this MODIFIED. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers |
The following was filed automatically by anaconda: anaconda 13.39 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devices.py", line 607, in setup raise DeviceError("device has not been created", self.name) File "/usr/lib/anaconda/storage/devices.py", line 2745, in setup member.setup(orig=orig) File "/usr/lib/anaconda/storage/deviceaction.py", line 312, in execute self.device.setup(orig=True) File "/usr/lib/anaconda/storage/devicetree.py", line 696, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 283, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 109, in turnOnFilesystems anaconda.storage.doIt() File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked self.anaconda.dispatch.gotoNext() DeviceError: ('device has not been created', 'sdb1')