Bug 862948

Summary: KickstartValueError: The following problem occurred on line 0 of the kickstart file: Requested boot drive vdb doesn't exist
Product: [Fedora] Fedora Reporter: Reartes Guillermo <rtguille>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, dcantrell, flokip, g.kaviyarasu, jonathan, michal.ambroz, rebus, vanmeeuwen+fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8652ab4d7f4a37bece5c56d08548f31dbbb03e5dc2c191bbd9bb4fbf1520e56c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-30 16:51:33 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
File: anaconda-tb
none
File: product
none
File: type
none
File: ifcfg.log
none
File: storage.log
none
File: version
none
File: environ
none
File: anaconda.log
none
File: syslog
none
File: hashmarkername
none
File: packaging.log
none
File: cmdline_file
none
File: release
none
File: program.log
none
I could not reproduce it (on two kvm guests) but i got this instead
none
the bug is alive none

Description Reartes Guillermo 2012-10-04 01:59:23 UTC 
Description of problem:
entered storage, it bombed after i deselected all disk and leave storage.

Version-Release number of selected component:
anaconda-18.11

Additional info:
libreport version: 2.0.14
cmdline:        /usr/bin/python  /sbin/anaconda
kernel:         3.6.0-1.fc18.x86_64

description:
:The following was filed automatically by anaconda:
:anaconda 18.11 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 314, in execute
:    msg="Requested boot drive %s doesn't exist" % self.bootDrive)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1557, in doKickstartStorage
:    ksdata.bootloader.execute(storage, ksdata, instClass)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 333, in _doExecute
:    doKickstartStorage(self.storage, self.data, self.instclass)
:  File "/usr/lib64/python2.7/threading.py", line 504, in run
:    self.__target(*self.__args, **self.__kwargs)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 87, in run
:    threading.Thread.run(self, *args, **kwargs)
:KickstartValueError: The following problem occurred on line 0 of the kickstart file:
:
:Requested boot drive vdb doesn't exist
:
Comment 1 Reartes Guillermo 2012-10-04 01:59:44 UTC 
Created attachment 621244 [details]
File: anaconda-tb
Comment 2 Reartes Guillermo 2012-10-04 01:59:48 UTC 
Created attachment 621245 [details]
File: product
Comment 3 Reartes Guillermo 2012-10-04 01:59:50 UTC 
Created attachment 621246 [details]
File: type
Comment 4 Reartes Guillermo 2012-10-04 01:59:52 UTC 
Created attachment 621247 [details]
File: ifcfg.log
Comment 5 Reartes Guillermo 2012-10-04 02:00:06 UTC 
Created attachment 621248 [details]
File: storage.log
Comment 6 Reartes Guillermo 2012-10-04 02:00:09 UTC 
Created attachment 621249 [details]
File: version
Comment 7 Reartes Guillermo 2012-10-04 02:00:12 UTC 
Created attachment 621250 [details]
File: environ
Comment 8 Reartes Guillermo 2012-10-04 02:00:14 UTC 
Created attachment 621251 [details]
File: anaconda.log
Comment 9 Reartes Guillermo 2012-10-04 02:00:19 UTC 
Created attachment 621252 [details]
File: syslog
Comment 10 Reartes Guillermo 2012-10-04 02:00:22 UTC 
Created attachment 621253 [details]
File: hashmarkername
Comment 11 Reartes Guillermo 2012-10-04 02:00:24 UTC 
Created attachment 621254 [details]
File: packaging.log
Comment 12 Reartes Guillermo 2012-10-04 02:00:26 UTC 
Created attachment 621255 [details]
File: cmdline_file
Comment 13 Reartes Guillermo 2012-10-04 02:00:29 UTC 
Created attachment 621256 [details]
File: release
Comment 14 Reartes Guillermo 2012-10-04 02:00:33 UTC 
Created attachment 621257 [details]
File: program.log
Comment 15 Jesse Keating 2012-10-05 00:51:25 UTC 
I can't reproduce this with anaconda-18.12 which is in the Beta TC2 compose.

Can you retest?

​http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC2/
Comment 16 Reartes Guillermo 2012-10-05 01:10:58 UTC 
Created attachment 621881 [details]
I could not reproduce it (on two kvm guests) but i got this instead

it says "no disk selected" and remains greyed out (reboot needed to relaunch anaconda).
Comment 17 Jesse Keating 2012-10-05 01:15:08 UTC 
Ok, I'm going to close this bug.  A new bug can be opened if you can reproduce the issue you just mentioned (after giving it a few minutes to reset)
Comment 18 Reartes Guillermo 2012-10-10 00:40:33 UTC 
Created attachment 624371 [details]
the bug is alive

i will try to reproduce it again to note the steps in detail, it took me by surprise to see this.
Comment 19 Reartes Guillermo 2012-10-10 00:42:02 UTC 
By the way, ABRT does not open another bug, it points to this one.
Comment 20 Reartes Guillermo 2012-10-10 00:43:13 UTC 
can this bug be re-opened?
Comment 21 Reartes Guillermo 2012-10-16 01:09:15 UTC 
i was trying to reproduce another bug.
i was switching back and forth manual to automatic partitioning and with either one, two disks.


Package: anaconda-18.16
OS Release: Fedora release 18-Beta-TC4
Comment 22 Reartes Guillermo 2012-10-20 03:48:00 UTC 
F18b TC5 (anaconda 18.18)

Package: anaconda-18.18
OS Release: Fedora release 18-Beta-TC5
Comment 23 Chris Lumens 2012-10-22 02:21:43 UTC 
*** Bug 868525 has been marked as a duplicate of this bug. ***
Comment 24 Chris Lumens 2012-11-14 15:30:50 UTC 
Are you still hitting this with anaconda-18.28 or later?
Comment 25 Michal Ambroz 2013-01-26 17:14:55 UTC 
1) booted LiveCD of Fedora 18 in order to upgrade/reinstall the installation on harddrive
I have created bootable USB disk for that

2) I choosed to install to harddrive

3) Clicked "Storage" in order to choose partitions which to overwrite

4) Clicked "Encrypt my data" as the LVM volume and standalone partitions I have are already encrypted

5) in "Installation options" popup dialog I choosed "I do not need help; let me customize disk partitioning"
and pushed "Reclaim space"

6) Manual partitioning dialog pop-ed up, but after while it crashes

I have really non-standard partitioning - I guess that some of that freaks the installator to death:
   Device		size		Id	System
/dev/sda1	050G	07	HPFS/NTFS/exFAT
/dev/sda2	004G   	83	/boot ext3
/dev/sda3	016G  	83	Ubuntu / ext3 encrypted
/dev/sda4        		05	Extended
/dev/sda5	016G	83	/ for Fedora - LUKS encrypted ext3
/dev/sda6	016G	83	/home - LUKS encrypted ext3
/dev/sda7	004G	83	swap - LUKS encrypted swapfs
/dev/sda8	050G	07	HPFS/NTFS/exFAT
/dev/sda9	320G	8e	LUKS encrypted LVM volume with 3 logical drives






Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18
Comment 26 Michal Ambroz 2013-01-26 19:10:51 UTC 
Trying to repartition drive.

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18
Comment 27 David Lehman 2013-05-30 16:51:33 UTC 
Closing this bug due to inactivity. Please reopen this bug and attach logs (/tmp/anaconda-tb-*) if you see this bug in Fedora 19 Beta or later.