Both task-upstream-atomic and task-fedora-cloud-tests fail with:
Traceback (most recent call last): File "/usr/bin/testcloud", line 11, in <module> load_entry_point('testcloud==0.1.11', 'console_scripts', 'testcloud')() File "/usr/lib/python2.7/site-packages/testcloud/cli.py", line 343, in main args.func(args) File "/usr/lib/python2.7/site-packages/testcloud/cli.py", line 97, in _create_instance tc_instance.start(args.timeout) File "/usr/lib/python2.7/site-packages/testcloud/instance.py", line 417, in start create_status = dom.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1039, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirt.libvirtError: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
https://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/731755/steps/runtask/logs/stdio
(and then they mark all results as NEEDS_INSPECTION, which is obviously wrong).
If we want to run these tests, we need to enable nested virt on our buildslaves. I'll disable these tasks until we do that, because there's no point in running them now.
Metadata Update from @kparal: - Issue priority set to: Normal - Issue tagged with: infra
Metadata Update from @tflink: - Issue assigned to tflink
This will be good to work on as we redeploy things. I thought we had already enabled nested virt on the client host boxes but apparently not :)
We have to decide whether we want to execute them at all, or not. Currently no one seems to consume them. For the record, those are these two tasks: https://pagure.io/taskotron/task-upstream-atomic https://pagure.io/taskotron/task-fedora-cloud-tests And then we have autocloud results being forwarded to resultsdb, which is most probably a different test suite than for the two above: https://taskotron.fedoraproject.org/resultsdb/results?&testcases=compose.cloud.all
Metadata Update from @kparal: - Assignee reset - Issue untagged with: infra - Issue priority set to: None (was: Normal)
Sigh, I was commenting on a cached ticket version. Good job, pagure. Fixing the fields.
Metadata Update from @kparal: - Issue assigned to tflink - Issue priority set to: Normal - Issue tagged with: infra
Login to comment on this ticket.