Unable to use virt-install in mock
Description
Activity
Former user December 20, 2018 at 2:02 PM
For now I've marked all Fedora VMs to only run builds with matching labels. could you please confirm if the builds stabilized? If so we can re-trigger all failed runs to ensure proper flags are set. Also, let's change the job settings as propsed by and add virt-host-validate to the script to have some debug info available from libvirt.
Barak Korren December 18, 2018 at 6:47 PM
When using libvirt, we always use libvirtd that is running on the host.
We've been mixing different distros in and out of mock for a while now, so what has changed?
In ay case it is possible to force that job to run mock on a host that runs the saem distro - in v1 its done via node-filter
, in v2 its done via host-distribution
in runtime-requirements
.
Former user December 18, 2018 at 3:10 PM
Looked at several of the failed jobs, like this one:
https://jenkins.ovirt.org/job/ovirt-appliance_standard-check-patch/35/
Loks like virtualization is on yet the el7 mock is running on a Fedora VM:
+ source /etc/os-release
++ NAME=Fedora
++ VERSION='28 (Cloud Edition)'
...
++ grep vmx
+ [[ -n flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm constant_tsc rep_good nopl cpuid pni pclmulqdq vmx ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm pti tpr_shadow vnmi flexpriority ept vpid arat
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm constant_tsc rep_good nopl cpuid pni pclmulqdq vmx ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm pti tpr_shadow vnmi flexpriority ept vpid arat ]]
+ is_nested_kvm_enabled
+ local i_nested_path=/sys/module/kvm_intel/parameters/nested
+ [[ -f /sys/module/kvm_intel/parameters/nested ]]
++ cat /sys/module/kvm_intel/parameters/nested
+ [[ Y != \N ]]
+ return 0
Later inside the mock we fail:
2018-12-18 12:45:29,564: Running virt-install.
ERROR Host does not support any virtualization options
Are we using the host's libvirt in the mock? If so, how do we add a node label limit for the check-patch parts of this job?
Some jenkins jobs that run virt-install (node-ng, appliance) randomly fail on "ERROR Host does not support any virtualization options".