Red Hat Bugzilla – Bug 853980
koan does not inject a kickstart file with qemu virtual install
Last modified: 2013-08-01 02:38:11 EDT
Description of problem:
running the command:
sudo koan --virt --virt-name=xxx --server=puppet --system=xxx
on a system with qemu based virtualisation does not inject the kickstart file into the boot process.
The output from:
in virt_net_install in app.py, after calling create_func, looks like this:
- ['virt-install', '--connect', 'qemu:///system', '--name', 'robot', '--ram', '1024', '--vcpus', '1', '--autostart', '--vnc', '--hvm', '--location', 'http://172.17.31.77/cblr/links/f17-i386/', '--arch', 'i386', '--os-variant', 'generic26', '--disk', 'path=/var/lib/libvirt/images//robot-disk0,size=5', '--network', 'bridge=vmbridge', '--mac=00:16:3e:4d:79:04', '--wait', '0', '--noautoconsole']
I think that the --hvm should also have the kickstart description appended to it. Lines 200-219 of /usr/lib/python2.7/site-packages/koan/virtinstall.py indicate that the --extra-args are not appended properly. If I delete the else: on 204 then the boot works ok, giving this output, and going on to act on the kickstart file:
- ['virt-install', '--connect', 'qemu:///system', '--name', 'robot', '--ram', '1024', '--vcpus', '1', '--autostart', '--vnc', '--hvm', '--extra-args=ks=http://172.17.31.77/cblr/svc/op/ks/system/robot ksdevice=link kssendmac lang= text ', '--location', 'http://172.17.31.77/cblr/links/f17-i386/', '--arch', 'i386', '--os-variant', 'generic26', '--disk', 'path=/var/lib/libvirt/images//robot-disk0,size=5', '--network', 'bridge=vmbridge', '--mac=00:16:3e:4d:79:04', '--wait', '0', '--noautoconsole']
Here's the relevant code snippet:
198 if is_qemu and virt_type:
199 if not disable_virt_type:
200 cmd += "--virt-type %s " % virt_type
201 if fullvirt or is_qemu or is_import:
202 if fullvirt is not None:
203 cmd += "--hvm "
205 cmd += ("--extra-args=\"%s\" " % (extra))
206 if is_xen:
207 cmd += "--pxe "
208 elif cdrom:
209 cmd += "--cdrom %s " % cdrom
210 elif location:
211 cmd += "--location %s " % location
212 elif importpath:
213 cmd += "--import "
214 if arch:
215 cmd += "--arch %s " % arch
217 cmd += "--paravirt "
218 cmd += ("--boot kernel=%s,initrd=%s,kernel_args=\"%s\" " %
219 (kernel, initrd, extra))
As I don't have anything more than my one installation, I've no idea whether just removing the else: appropriate or sufficient.
Version-Release number of selected component (if applicable):
Unclear - I'm not sure what are the key components involved in this scenario. However, assuming that it's just qemu and koan, it seems to be consistent.
Steps to Reproduce:
1. import an f17 profile
2. define a system based on the profile with a kickstart file
3. run the above koan command
kickstart not used by anaconda on the vm. Built command does not include --extra-args parameter
vm should launch and install using the kickstart.
This is fixed in cobbler git:
Author: Daichi Kamemoto <email@example.com>
Date: Sat Jun 23 22:59:55 2012 +0900
BUGFIX extra-args option problems
- fix qemu haven't extra-args.
- fix empty 'extra' params added 'extra-args=None' to virt-install.
What does it take to get a new version of cobbler released? And a Fedora build?
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
Actually, I think it was fixed in Fedora 17 on 20th June in koan-2.4.0. I don't appear to be able to change the status though.