Hello all!
Let me preface the following with : Not sure if this is a cobbler / koan
issue or a F10 issue
Imported F10 into cobbler and created a f10.ks (copy of my f9.ks with a
repo location change), everything looks fine from the cobbler side
[cobbler]# cobbler profile report --name=f9-i386
profile : f9-i386
distro : f9-i386
dhcp tag : default
kernel options : {}
post kernel options : {'console': ['ttyS1,57600', 'tty1']}
kickstart : /etc/cobbler/fc9.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : br9
virt cpus : 1
virt file size : 7
virt path : /mnt/os1
virt ram : 1024
virt type : qemu
[cobbler]# cobbler profile report --name=f10-i386
profile : f10-i386
distro : f10-i386
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/f10.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : br9
virt cpus : 1
virt file size : 7
virt path : /mnt/os1
virt ram : 1024
virt type : qemu
I can kick of a koan for the f9-i386 cobbler profile and everything runs
as expected, when I the f10-i386 profile the install hangs setting up
eth0 via NM (Netowkr Manager) which errors out and gives a retry button.
Clicking the retry button kicks F10 in the arse, eth0 is configured, a
DHCPREQUEST is fired off and everything goes smooth from there.
Went as far as doing a virt-install and compared the auto generated
anaconda.ks to my f10.ks and found no diff with the network setup.
Any thoughts?
-Ron
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
