Bug 1044680 - ValueError: cannot initialize a disk that has partitions
Summary: ValueError: cannot initialize a disk that has partitions
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:546b3931b3e1eb2b2718a73f494...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 19:42 UTC by xq1xq1xq1
Modified: 2014-01-15 18:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-15 18:47:19 UTC
Type: ---


Attachments (Terms of Use)
File: anaconda-tb (259.54 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: anaconda.log (4.38 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: environ (510 bytes, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: ks.cfg (18.24 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: lsblk_output (1.72 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: nmcli_dev_list (4.65 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: os_info (179 bytes, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: program.log (24.05 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: storage.log (57.78 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: syslog (118.60 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: ifcfg.log (846 bytes, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
File: packaging.log (2.10 KB, text/plain)
2013-12-18 19:42 UTC, xq1xq1xq1
no flags Details
Anaconda Traceback File (257.46 KB, text/plain)
2013-12-19 16:02 UTC, xq1xq1xq1
no flags Details
KS.CFG File (16.38 KB, text/plain)
2013-12-19 16:04 UTC, xq1xq1xq1
no flags Details

Description xq1xq1xq1 2013-12-18 19:42:02 UTC
Description of problem:
Building a Fedora 19 using a USB Flash Drive Automated Kickstart Configuration

Version-Release number of selected component:
anaconda-19.30.13-1

The following was filed automatically by anaconda:
anaconda 19.30.13-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 810, in initializeDisk
    raise ValueError("cannot initialize a disk that has partitions")
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 785, in clearPartitions
    self.initializeDisk(disk)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 488, in execute
    storage.clearPartitions()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1639, in doKickstartStorage
    ksdata.clearpart.execute(storage, ksdata, instClass)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/spokes/storage.py", line 253, in execute
    doKickstartStorage(self.storage, self.data, self.instclass)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 49, in setup
    spoke.execute()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/__init__.py", line 165, in setup
    obj.setup(self.ENVIRONMENT)
  File "/sbin/anaconda", line 1086, in <module>
    anaconda._intf.setup(ksdata)
ValueError: cannot initialize a disk that has partitions

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img nousbstorage xdriver=vesa nomodeset ks=hd:/dev/disk/by-label/BOOT:/ks.cfg repo=hd:LABEL=Fedora:/Fedora BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.5-301.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19

Comment 1 xq1xq1xq1 2013-12-18 19:42:08 UTC
Created attachment 838540 [details]
File: anaconda-tb

Comment 2 xq1xq1xq1 2013-12-18 19:42:09 UTC
Created attachment 838541 [details]
File: anaconda.log

Comment 3 xq1xq1xq1 2013-12-18 19:42:11 UTC
Created attachment 838542 [details]
File: environ

Comment 4 xq1xq1xq1 2013-12-18 19:42:12 UTC
Created attachment 838543 [details]
File: ks.cfg

Comment 5 xq1xq1xq1 2013-12-18 19:42:14 UTC
Created attachment 838544 [details]
File: lsblk_output

Comment 6 xq1xq1xq1 2013-12-18 19:42:15 UTC
Created attachment 838545 [details]
File: nmcli_dev_list

Comment 7 xq1xq1xq1 2013-12-18 19:42:17 UTC
Created attachment 838546 [details]
File: os_info

Comment 8 xq1xq1xq1 2013-12-18 19:42:18 UTC
Created attachment 838547 [details]
File: program.log

Comment 9 xq1xq1xq1 2013-12-18 19:42:20 UTC
Created attachment 838548 [details]
File: storage.log

Comment 10 xq1xq1xq1 2013-12-18 19:42:22 UTC
Created attachment 838549 [details]
File: syslog

Comment 11 xq1xq1xq1 2013-12-18 19:42:25 UTC
Created attachment 838550 [details]
File: ifcfg.log

Comment 12 xq1xq1xq1 2013-12-18 19:42:26 UTC
Created attachment 838551 [details]
File: packaging.log

Comment 13 xq1xq1xq1 2013-12-19 16:02:25 UTC
Created attachment 839061 [details]
Anaconda Traceback File

Comment 14 xq1xq1xq1 2013-12-19 16:04:35 UTC
Created attachment 839062 [details]
KS.CFG File


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