Bug 506572

Summary: Attempting to Upgrade from FC10
Product: [Fedora] Fedora Reporter: Skip <skip>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, bmdrake919, jvonau3, michal, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:3fea10818b0712f4da707ae30dae38be4593b657020d855778c6fb7458a15cf8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-17 20:07:01 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
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description Skip 2009-06-17 19:14:57 UTC
The following was filed automatically by anaconda:
anaconda 11.5.0.59 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/formats/__init__.py", line 289, in setup
    raise FormatSetupError("invalid device specification")
  File "/usr/lib/anaconda/storage/formats/swap.py", line 118, in setup
    DeviceFormat.setup(self, *args, **kwargs)
  File "/usr/lib/anaconda/storage/__init__.py", line 1581, in turnOnSwap
    device.format.setup()
  File "/usr/lib/anaconda/upgrade.py", line 313, in upgradeMountFilesystems
    anaconda.id.storage.fsset.turnOnSwap(anaconda, upgrading=True)
  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 1339, in nextClicked
    self.anaconda.dispatch.gotoNext()
FormatSetupError: invalid device specification

Comment 1 Skip 2009-06-17 19:15:03 UTC
Created attachment 348326 [details]
Attached traceback automatically from anaconda.

Comment 2 Bruce Drake 2009-06-21 21:30:33 UTC
Created attachment 348822 [details]
Attached traceback automatically from anaconda.

Comment 3 Bruce Drake 2009-06-21 21:35:03 UTC
Prior to experiencing this exception (see comment #2), I had another error, which displayed in a pop-up saying something like device sdb unreadable, ignore or reinitalize.  I selected ignore because that device is one of my MSWindows volumes.  Don't know if this is related or not.

Comment 4 Chris Lumens 2009-07-17 20:07:01 UTC

*** This bug has been marked as a duplicate of bug 505725 ***

Comment 5 Michal Jaegermann 2009-07-27 17:55:43 UTC
Created attachment 355301 [details]
Attached traceback automatically from anaconda.

Comment 6 Michal Jaegermann 2009-07-27 19:17:09 UTC
I am not sure why an automatic submission classified that in this report.
An ultimate error appears to be

ImportError: cannot import name CTC

triggered by an attempt to convert a firewall configuaration and associated with a segfault while running some triggers for system-firewall-config package.

I removed that offending package and the whole update is running right now (with still some two hundreds packages to go).

Comment 7 Jerry Vonau 2009-08-05 01:45:35 UTC
Created attachment 356249 [details]
Attached traceback automatically from anaconda.

Comment 8 Jerry Vonau 2009-08-05 05:39:30 UTC
Mine appears to be caused by the "swap in fstab" issue, my swap lives on LVM