-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Cirrus: Update Ubuntu VM images #10709
Conversation
5be6b91
to
9efcf62
Compare
/hold forever |
bdflush syscall permission denied problem from buildah PR is reproducing here also. using freshly built image c4805484248039424. Trying the image I built 3-days earlier: c4635821094469632 |
|
f4c50f6
to
d1a611c
Compare
Hrmmmm, it passed, that was unexpected. |
d1a611c
to
f95e4d7
Compare
ceedca9
to
35cb78b
Compare
Ugh, this is really strange. Fedora 33/34 think the /dev/kvm device doesn't exist and the Ubuntus throw an error inside the container. |
Okay right...the Fedora problem is explainable - we're using really old images due to need of an SELinux-related updated (IIRC, already working it's way through the system). Ignoring this for now. The Ubuntu failures are a true anomaly though. I did go into a VM and verify the device (on the host) does exist. @mheon these VM's have just had nested-virt enabled on them (previously it was disabled). I'm guessing this is why the Ubuntu test failures got missed: The device node wasn't there, now it is (test skips if file is missing). Is this even a valid test to run in rootless mode? Maybe should I switch the test to use a less-special device, like |
35cb78b
to
5cc1f86
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cevich The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I think the SELinux issues should be fixed in Fedora now. |
Oh great, thanks for reminding me. I'll revert that change. |
These images include a fix for: containers/common#631 Signed-off-by: Chris Evich <[email protected]>
This reverts commit 404d5ed. Also minor update to an unrelated FIXME comment. Signed-off-by: Chris Evich <[email protected]>
This test has been failing for a long time but nobody noticed because CI doesn't have the device node (nested-VM support was disabled). After having enabled nested VM support, tests fail due to some unknown special-handling of this device. Fix both problems by removing the `skip()` and switching to a more generic device which is only present when `--privileged` is used. Signed-off-by: Chris Evich <[email protected]>
5cc1f86
to
ddfdd16
Compare
Oof, what did I do 😕 |
Re-opened as #10829 |
These images include a fix for:
containers/common#631