Hi,

I used 'network --device=00:22:19:5A:40:BF ... ' in kickstart file:

network --bootproto=static --device=00:22:19:5a:40:bf --gateway=...
--hostname=... --ip=... --netmask=255.255.252.0
network --bootproto=static --device=00:22:19:5a:40:c1 --gateway=...
--hostname=... --ip=... --nameserver=... --netmask=255.255.252.0
network --bootproto=static --device=00:15:17:97:80:ac --ip=...
--netmask=255.255.252.0

and anaconda had a problem with that (see below traceback message).
Is this an anaconda bug or am I missing something in the kickstart?


==========================
Traceback (most recent call first):
File "/usr/lib/anaconda/network.py", line 407, in setGateway
self.netdevices[device].set(('GATEWAY', gw))
File "/usr/lib/anaconda/kickstart.py", line 618, in execute
anaconda.id.network.setGateway(self.gateway, device)
File "/usr/lib/anaconda/kickstart.py", line 1149, in execute
obj.execute(self.anaconda)
File "/usr/bin/anaconda", line 1102, in <module>
ksdata.execute()
KeyError: '00:22:19:5a:40:bf'

id.network: Network instance, containing members:
id.network.netdevices: {'eth5': DEVICE="eth5"
BOOTPROTO="dhcp"
DNS1="10.126.125.5"
HWADDR="00:22:19:5A:40:C1"
NM_CONTROLLED="yes"
ONBOOT="yes"

, 'eth4': DEVICE="eth4"
BOOTPROTO="static"
HWADDR="00:22:19:5A:40:BF"
IPADDR="147.165.51.172"
NETMASK="255.255.252.0"
NM_CONTROLLED="yes"
ONBOOT="yes"

, 'eth3': DEVICE="eth3"
HWADDR="00:15:17:97:80:CB"
NM_CONTROLLED="yes"
ONBOOT="no"

, 'eth2': DEVICE="eth2"
HWADDR="00:15:17:97:80:CA"
NM_CONTROLLED="yes"
ONBOOT="no"

, 'eth1': DEVICE="eth1"
HWADDR="00:15:17:97:80:AD"
NM_CONTROLLED="yes"
ONBOOT="no"

, 'eth0': DEVICE="eth0"
HWADDR="00:15:17:97:80:AC"
NM_CONTROLLED="yes"
ONBOOT="no"

}
========================


Thanks,
rmu

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On 04/02/2011 12:15 PM, Romu wrote:

Hi,

I used 'network --device=00:22:19:5A:40:BF ... ' in kickstart file:

network --bootproto=static --device=00:22:19:5a:40:bf --gateway=...
--hostname=... --ip=... --netmask=255.255.252.0
network --bootproto=static --device=00:22:19:5a:40:c1 --gateway=...
--hostname=... --ip=... --nameserver=... --netmask=255.255.252.0
network --bootproto=static --device=00:15:17:97:80:ac --ip=...
--netmask=255.255.252.0

and anaconda had a problem with that (see below traceback message).
Is this an anaconda bug or am I missing something in the kickstart?



The kickstart looks ok - it is an anaconda bug, I filed
http://bugzilla.redhat.com/show_bug.cgi?id=693302
for Fedora 15. For rhel 6 it should be fixed in current
version of anaconda (6.1 beta).

Radek

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list