Bug 223903

Summary:	AttributeError: Partition instance has no attribute 'anaconda'
Product:	[Fedora] Fedora	Reporter:	Orion Poplawski <orion>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-01-23 15:26:31 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:

Description Orion Poplawski 2007-01-22 23:15:26 UTC

From 20070122 rawhide:

self.commands[cmd].parse(cmdArgs)
File "/usr/lib/anaconda/kickstart.py", line 494, in parse
addPartRequest(self.anaconda, request)
AttributeError: Partition instance has no attribute 'anaconda'

kickstart header:

install
text
nfs --server=saga --dir=/export/data1/fedora/core/development/i386/os
lang en_US.UTF-8
keyboard us
network --bootproto=dhcp
rootpw --iscrypted CwU/lYtazWt7E
firewall --disabled
selinux --enforcing
authconfig --enableshadow --enablenis --nisdomain=yp.colorado-research.com
timezone America/Denver
xconfig --startxonboot --defaultdesktop=KDE --resolution=1600x1200 --depth=24
bootloader --location=mbr --driveorder=sda
clearpart --linux --drives=sda
part /boot --fstype ext3 --size=50
part pv.1 --size 4800 --grow
volgroup rootvg pv.1
logvol / --vgname=rootvg --size=512 --name=root
logvol swap --fstype=swap --vgname=rootvg --recommended --name=swap
logvol /usr --vgname=rootvg --size=4500 --name=usr
logvol /var --vgname=rootvg --size=512 --name=var
logvol /export/data1 --vgname=rootvg --size=1 --name=data1 --grow
reboot


Also seen of VT2:

-/bin/sh: error while loading shared libraries: libncurses.so.5: cannot open
shared object file: No such file or directory

Comment 1 Chris Lumens 2007-01-23 15:26:31 UTC

Thanks for the report.  This (and a couple other instances of the same thing)
will be fixed in the next build.