Bug 489595

Summary: [StorageRewrite] - ValueError: pv is not in the device tree
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: anaconda-maint-list, jturner, pjones, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:5adc4e5fe261888f112b39bb4b1c9293a89e164808a7fa2f95967f2dc32e8128
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-16 18:12:03 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:
Attachments:
Description Flags
Attached traceback automatically from anaconda. none

Description James Laska 2009-03-10 20:29:52 UTC
The following was filed automatically by anaconda:
anaconda 11.5.0.26 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/__init__.py", line 521, in newVG
    raise ValueError("pv is not in the device tree")
  File "/usr/lib/anaconda/storage/partitioning.py", line 163, in doAutoPartition
    vg = anaconda.id.storage.newVG(pvs=pvs)
  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()
ValueError: pv is not in the device tree

Comment 1 James Laska 2009-03-10 20:29:56 UTC
Created attachment 334711 [details]
Attached traceback automatically from anaconda.

Comment 2 Chris Lumens 2009-03-16 17:50:16 UTC
We think this is a duplicate of the dev vs. devs bug (don't think that ever got filed, but Joel did commit a patch for it).  Can you try the latest build and verify that we've fixed this up?  Thanks.

Comment 3 James Laska 2009-03-16 18:12:03 UTC
I'm not seeing this with todays build.  I am now seeing bug#490296 which should be fixed in tomorrows images.