Bug 527711 - Ignoring a disk and then later on initializing it causes a backtrace
Summary: Ignoring a disk and then later on initializing it causes a backtrace
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 526895 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-07 12:49 UTC by Hans de Goede
Modified: 2010-03-12 09:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-12 09:08:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hans de Goede 2009-10-07 12:49:07 UTC
To reproduce:

1) have a disk in your system without a partition label on it
2) choose to ignore it (for example by blindly pressing enter)
3) arrive at partition method screen, anaconda only sees usb-stick it booted
   from, press next
4) anaconda says not enough free space, press ok
5) anaconda rescans disks
6) press intialize this time for the same disk
7) select "new" disk as disk to install to
8) press next
9) write changes -> yes
10) backtrace because pvcreate failed, because the disk is in
   lvm's devices to filter list from the initial ignore disk

Chris: note please do not assign this one to me.

(I know I know this is a don't do that you silly, but still we ought to do
 better).

Comment 1 Bug Zapper 2009-11-16 13:21:42 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Hans de Goede 2009-11-24 10:08:59 UTC
Copy paste from irc so this does not get lost:

I see 2 ways of fixing this:

1) only ask only once to initialize a disk (probably easiest and makes sense for other cases where we re-scan storage too) this can probably be done by simply checking the disk is not being ignored before asking for initialization . Actually this makes sense to do in general, asking to init a disk which we've somehow been told to ignore is rather lame.

2) Another option would be to remove disks from the ignore list (and lvm filter) when they get initialized, but I like the first option more and it is also easier to implement.

Comment 3 Radek Vykydal 2009-12-22 16:59:55 UTC
The traceback is fixed with commit f6f23c29ac4a6a2035bc8a67aafecd41c5414a95. I am also working on a patch (it is in review process) that will reduce asking in dialog only to "storageinit" step.

Comment 4 Hans de Goede 2010-01-04 11:13:07 UTC
*** Bug 526895 has been marked as a duplicate of this bug. ***

Comment 5 Radek Vykydal 2010-03-12 09:08:41 UTC
(In reply to comment #3)
> The traceback is fixed with commit f6f23c29ac4a6a2035bc8a67aafecd41c5414a95.

fixed in version 13.12 of anaconda

> I am also working on a patch (it is in review process) that will reduce asking in
> dialog only to "storageinit" step.    

went into version 13.17 of anaconda


Note You need to log in before you can comment on or make changes to this bug.