Bug 592337

+++ This bug was initially created as a clone of Bug #588597 +++

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')

--- Additional comment from jkeating on 2010-05-03 22:54:49 EDT ---

Created an attachment (id=411171)
Attached traceback automatically from anaconda.

--- Additional comment from jkeating on 2010-05-03 22:57:45 EDT ---

I got this when going from a system with two md devices to a default partitioning.

Tossing on the blocker list for visibility.

--- Additional comment from jlaska on 2010-05-04 15:45:02 EDT ---

Same as bug#568759 ?

--- Additional comment from jkeating on 2010-05-04 17:00:20 EDT ---

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.

--- Additional comment from awilliam on 2010-05-04 19:55:38 EDT ---

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.

--- Additional comment from jkeating on 2010-05-05 14:17:22 EDT ---

Created an attachment (id=411701)
Attached traceback automatically from anaconda.

--- Additional comment from jkeating on 2010-05-05 14:18:31 EDT ---

Seems this is still happening with 13.40

--- Additional comment from jlaska on 2010-05-06 18:10:30 EDT ---

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

--- Additional comment from jkeating on 2010-05-06 18:25:29 EDT ---

Makes it work here.

--- Additional comment from awilliam on 2010-05-06 22:24:37 EDT ---

that would make it fixed in 13.41, right?