-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KVM / virt nodes ? #654
Comments
@pabelanger @goneri Can you please help/advise with this? This job really needs virtualization support, maybe we have specific nodesets we can mention to avoid failing randomly. @apatard Were you able to find failures on other nodes than centos-8 or is specific to them? -- I see jobs running on other platforms at https://github.com/ansible-community/molecule-vagrant/blob/master/zuul.d/layout.yaml#L14-L17 |
No, it's not specific to centos. For instance, this old log on fedora: https://dashboard.zuul.ansible.com/t/ansible/build/8218cc176f9f401fbdbe16fe07b4f2a9/log/job-output.txt |
I removed centos-8 from AWS for now, ansible-network/windmill-config#740. I will see later how we can properly identify the nodes with the kvm capability and the others (EC2). |
molecule-vagrant is needing support for virtualization and from time to time, the tests are failing due to missing support for virtualization. The tests are failing like this:
(ref: https://dashboard.zuul.ansible.com/t/ansible/build/426dd647e97141b9b87f49b6a4c4b364/log/job-output.txt)
Not only it makes the testsuite fail randomly, but it's also a waste of resources.
Is there a way to run tests only on hosts providing virtualization ?
The text was updated successfully, but these errors were encountered: