Bug 759960 - ValueError: MDRaidArrayDevice ... is not in list
Summary: ValueError: MDRaidArrayDevice ... is not in list
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ea18beb79ac56243d61d00b80fc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-05 01:47 UTC by Michael Glasgow
Modified: 2013-02-13 08:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 08:43:54 UTC
Type: ---


Attachments (Terms of Use)
File: anaconda-tb-EaTNNf (1.29 MB, text/plain)
2011-12-05 01:48 UTC, Michael Glasgow
no flags Details

Description Michael Glasgow 2011-12-05 01:47:48 UTC
libreport version: 2.0.6
executable:     /usr/bin/python
hashmarkername: anaconda
kernel:         3.1.0-7.fc16.x86_64
product:        Fedora
time:           Sun Dec  4 16:59:37 2011
version:        16

anaconda-tb-EaTNNf: Binary file, 1354198 bytes

description:
:The following was filed automatically by anaconda:
:anaconda 16.25 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1038, in grub_device_name
:    name = "(hd%d" % self.drives.index(drive)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1383, in grub_conf_device_line
:    return "device %s %s\n" % (self.grub_device_name(self.stage2_device),
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1151, in write_config_header
:    config.write(self.grub_conf_device_line)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 944, in write_config
:    self.write_config_header(config, install_root=install_root)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1266, in write_config
:    super(GRUB, self).write_config(install_root=install_root)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1450, in write
:    self.write_config(install_root=install_root)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2123, in writeBootloader
:    anaconda.bootloader.write(install_root=anaconda.rootPath)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch
:    self.dir = self.steps[self.step].target(self.anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward
:    self.dispatch()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked
:    self.anaconda.dispatch.go_forward()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback
:    self.intf.icw.nextClicked()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1221, in handleRenderCallback
:    self.currentWindow.renderCallback()
:ValueError: MDRaidArrayDevice instance (0x7f215eab6090) --
:  name = md0  status = True  kids = 0 id = 89
:  parents = ['existing 470MB partition sda2 (76) with non-existent mdmember',
: 'existing 470MB partition sdb2 (70) with non-existent mdmember']
:  uuid = 19d03e72:74a7f323:d7ba226b:f24b7792  size = 469.98828125
:  format = existing ext4 filesystem mounted at /boot
:  major = 0  minor = 0  exists = True  protected = False
:  sysfs path = /devices/virtual/block/md0  partedDevice = parted.Device instance --
:  model: Linux Software RAID Array  path: /dev/md0  type: 17
:  sectorSize: 512  physicalSectorSize:  512
:  length: 962536  openCount: 0  readOnly: False
:  externalMode: False  dirty: False  bootDirty: False
:  host: 32545  did: 0  busy: True
:  hardwareGeometry: (120317, 2, 4)  biosGeometry: (59, 255, 63)
:  PedDevice: <_ped.Device object at 0x7f2161961560>
:  target size = 0  path = /dev/md0
:  format args = None  originalFormat = ext4  level = 1  spares = 0
:  members = 2
:  total devices = 2  metadata version = 1.0 is not in list

reason:
:ValueError: MDRaidArrayDevice instance (0x7f215eab6090) --
:  name = md0  status = True  kids = 0 id = 89
:  parents = ['existing 470MB partition sda2 (76) with non-existent mdmember',
: 'existing 470MB partition sdb2 (70) with non-existent mdmember']
:  uuid = 19d03e72:74a7f323:d7ba226b:f24b7792  size = 469.98828125
:  format = existing ext4 filesystem mounted at /boot
:  major = 0  minor = 0  exists = True  protected = False
:  sysfs path = /devices/virtual/block/md0  partedDevice = parted.Device instance --
:  model: Linux Software RAID Array  path: /dev/md0  type: 17
:  sectorSize: 512  physicalSectorSize:  512
:  length: 962536  openCount: 0  readOnly: False
:  externalMode: False  dirty: False  bootDirty: False
:  host: 32545  did: 0  busy: True
:  hardwareGeometry: (120317, 2, 4)  biosGeometry: (59, 255, 63)
:  PedDevice: <_ped.Device object at 0x7f2161961560>
:  target size = 0  path = /dev/md0
:  format args = None  originalFormat = ext4  level = 1  spares = 0
:  members = 2
:  total devices = 2  metadata version = 1.0 is not in list

Comment 1 Michael Glasgow 2011-12-05 01:48:07 UTC
Created attachment 540575 [details]
File: anaconda-tb-EaTNNf

Comment 3 Michael Glasgow 2011-12-15 11:20:58 UTC
Repeat by:

Try to install F16 netinst where:

md0 = /boot
md1 = encrypted, LVM physical volume

and the rest of the system is in a volume group on md1.

Should be simple to reproduce.

Comment 4 Jesse Keating 2012-07-19 21:22:42 UTC
Is this still a problem with F17?  Our EFI stuff has changed quite a bit since f16.

Comment 5 Fedora End Of Life 2013-01-16 10:12:23 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Fedora End Of Life 2013-02-13 08:44:18 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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


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