Hullo I've recently preupgrade-cli'd a box from f15 to f17 and now my koan/cobbler builds no longer inject kickstart files.
Even if I take the stock /var/lib/cobbler/kickstarts/sample.ks and use it as the ks for a profile, when I run: sudo koan --virt --virt-name=robot --server=puppet --system=robot [robot's defined as being based on f17-i386 profile, which has a Kickstart using the sample.ks above] After powering up, the vm starts a graphical install and seems to have no knowledge of the kickstart file. If I take it through the graphical install, the /root/anaconda-ks.cfg is the default created by anaconda. Nothing gives the game away when I log into the VM's console during the installation. It doesn't seem to matter if I use an older profile (I've tried F15). I'm using cobbler-2.2.3-2.fc17.noarch, and koan-2.2.3-2.fc17.noarch sudo cobbler validateks doesn't complain (I had to fix the $kickstart_start/$kickstart_done in the old kickstarts, but these are not present in the sample.ks). The only oddities that I can identify are /var/log/messages entries like these: Sep 3 10:28:18 mercury libvirtd[4807]: 2012-09-03 09:28:18.284+0000: 4808: error : virSecurityDACRestoreSecurityFileLabel:148 : cannot resolve symlink /var/lib/libvirt/boot/virtinst-vmlinuz. 5LB4JW: No such file or directory Sep 3 10:28:18 mercury libvirtd[4807]: 2012-09-03 09:28:18.284+0000: 4808: error : virSecurityDACRestoreSecurityFileLabel:148 : cannot resolve symlink /var/lib/libvirt/boot/virtinst-initrd.i mg.fhjuOM: No such file or directory which could imply that there's something odd that's preventing the libvirtd setting up the boot filesystem, but I don't know enough about the innards to work that out. sudo rpm -V libvirtd shows no errors. Any pointers on how to work out what's going wrong/how to identify what's going wrong? Tim _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler
