revisor

#195 crash in kickstart raid
Closed: Fixed Opened by lfarkas@lfarkas.org.

Closed: Fixed
Reopen Issue

hi,
when i run revisor-2.0.4.0-1.fc7 with one of our kickstart file i always got this error:

Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/revisor/ready_screen.py", line 165, in button_forward_clicked
self.gui.displayBuildMedia()
File "/usr/lib/python2.5/site-packages/revisor/gui.py", line 255, in displayBuildMedia
self.BuildMedia.start()
File "/usr/lib/python2.5/site-packages/revisor/build_media.py", line 69, in start
self.base.lift_off()
File "/usr/lib/python2.5/site-packages/revisor/base.py", line 460, in lift_off
self.buildInstallationMedia()
File "/usr/lib/python2.5/site-packages/revisor/base.py", line 679, in buildInstallationMedia
f.write(self.cfg.kshandler.str())
File "/usr/lib/python2.5/site-packages/pykickstart/base.py", line 215, in str
retval += obj.str()
File "/usr/lib/python2.5/site-packages/pykickstart/commands/raid.py", line 111, in str
retval += raid.str()
File "/usr/lib/python2.5/site-packages/pykickstart/commands/raid.py", line 55, in str
return "raid %s %s %s\n" % (self.mountpoint, self._argsToStr(),
File "/usr/lib/python2.5/site-packages/pykickstart/commands/raid.py", line 89, in _argsToStr
retval = FC4_RaidData._argsToStr()
TypeError: unbound method _argsToStr() must be called with FC4_RaidData instance as first argument (got nothing instead)

possible reason can be that we use raid6 in this config:

clearpart --initlabel --all --drives=sda,sdb,sdc,sdd

part raid.11 --size=100 --asprimary --ondisk=sda
part raid.12 --size=100 --asprimary --ondisk=sdb
part raid.13 --size=100 --asprimary --ondisk=sdc
part raid.14 --size=100 --asprimary --ondisk=sdd
part raid.21 --size=1 --grow --ondisk=sda
part raid.22 --size=1 --grow --ondisk=sdb
part raid.23 --size=1 --grow --ondisk=sdc
part raid.24 --size=1 --grow --ondisk=sdd

raid /boot --fstype ext3 --level=1 --device=md0 raid.11 raid.12 raid.13 raid.14
raid pv.01 --level=6 --device=md1 raid.21 raid.22 raid.23 raid.24

volgroup VolGroup00 pv.01
logvol swap --fstype swap --name=LogVol00 --vgname=VolGroup00 --size=4096
logvol / --fstype ext3 --name=LogVol01 --vgname=VolGroup00 --size=3072
logvol /var --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=2048
logvol /srv --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=1 --grow

but why revisor care about kickstart raid config? it'd have to place the config file into the root dir and the installer will take care about the partitioning!?

This could be a pykickstart error having nothing to do with Revisor except for the fact we use pykickstart to parse kickstart configuration files with.

What does ksvalidator say about this kickstart file? Could you attach the complete kickstart file? Remember to remove any passwords that may be in there.

This could be a pykickstart error having nothing to do with Revisor except for the fact we use pykickstart to parse kickstart configuration files with.

What does ksvalidator say about this kickstart file? Could you attach the complete kickstart file? Remember to remove any passwords that may be in there.

the problematic file
x-i386.cfg

the problematic file
x-i386.cfg

but the same kickstart file is working with pxe boot!!! which is strange.

but the same kickstart file is working with pxe boot!!! which is strange.

and fill a bug at:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246709

and fill a bug at:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246709

but until this bug (or may be any kind of further pykickstart bug) will be fixed a simple workaround would be if pykickstart fail than simple copy the original kickstart file to the result iso image.

but until this bug (or may be any kind of further pykickstart bug) will be fixed a simple workaround would be if pykickstart fail than simple copy the original kickstart file to the result iso image.

Fixed upstream.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246709#c5

Fixed upstream.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246709#c5

Metadata Update from @lfarkas@lfarkas.org:
- Issue assigned to kanarip
- Issue set to the milestone: 2.0.4 Release
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.