Bug 924955

Summary: FormatCreateError: ('invalid device specification', '/dev/md/ws243.hanzlici.cz:home')
Product: [Fedora] Fedora Reporter: Frantisek Hanzlik <franta>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora, xordspar0
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:b2f528c531c170b917b3d87382fdebe1201e6b0563e855eb473667b5acd20a28
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:13:17 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: anaconda.log
none
File: environ
none
File: ifcfg.log
none
File: ks.cfg
none
File: packaging.log
none
File: program.log
none
File: storage.log
none
File: syslog none

Description Frantisek Hanzlik 2013-03-22 23:41:59 UTC
Description of problem:
installing f18 on system with two disks, using kickstart file, source repositories are on local NFS server.
anaconda crashes after specifying storage layout, in phase where own package installation (or maybe partition formating) should start. System disks was GPT partitioned and there was created five RAID1 MD disks before installation.
The following was filed automatically by anaconda:
anaconda 18.37.11 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/__init__.py", line 304, in create
    raise FormatCreateError("invalid device specification", self.device)
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 850, in create
    DeviceFormat.create(self, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 439, in execute
    options=self.device.formatArgs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 323, in processActions
    action.execute()
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 323, in doIt
    self.devicetree.processActions()
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 174, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib/python2.7/site-packages/pyanaconda/install.py", line 114, in doInstall
    turnOnFilesystems(storage)
  File "/usr/lib/python2.7/threading.py", line 504, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 91, in run
    threading.Thread.run(self, *args, **kwargs)
FormatCreateError: ('invalid device specification', '/dev/md/ws243.hanzlici.cz:home')

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20i386 ks=http://ws22/f18srvkom-ks.cfg BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.6.10-4.fc18.i686
other involved packages: 
package:        anaconda-18.37.11
product:        Fedora
release:        Cannot get release name.
type:           libreport
version:        18

Comment 1 Frantisek Hanzlik 2013-03-22 23:42:17 UTC
Created attachment 714844 [details]
File: anaconda-tb

Comment 2 Frantisek Hanzlik 2013-03-22 23:42:20 UTC
Created attachment 714845 [details]
File: anaconda.log

Comment 3 Frantisek Hanzlik 2013-03-22 23:42:22 UTC
Created attachment 714846 [details]
File: environ

Comment 4 Frantisek Hanzlik 2013-03-22 23:42:24 UTC
Created attachment 714847 [details]
File: ifcfg.log

Comment 5 Frantisek Hanzlik 2013-03-22 23:42:26 UTC
Created attachment 714848 [details]
File: ks.cfg

Comment 6 Frantisek Hanzlik 2013-03-22 23:42:28 UTC
Created attachment 714849 [details]
File: packaging.log

Comment 7 Frantisek Hanzlik 2013-03-22 23:42:33 UTC
Created attachment 714850 [details]
File: program.log

Comment 8 Frantisek Hanzlik 2013-03-22 23:42:41 UTC
Created attachment 714851 [details]
File: storage.log

Comment 9 Frantisek Hanzlik 2013-03-22 23:42:46 UTC
Created attachment 714852 [details]
File: syslog

Comment 10 Fedora End Of Life 2013-12-21 12:24:20 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2014-02-05 20:13:17 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.