-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[V3.3] Update images #11163
[V3.3] Update images #11163
Conversation
LGTM |
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cevich, mheon, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Note: I'm going to hold of updating this PR, since the test fixes are so similar to #10829 |
9128c55
to
bf23b48
Compare
346005b
to
0b00a2f
Compare
0b00a2f
to
af4db42
Compare
Previously we were generating the annotated results but never uploading them. Fix this so visiting the advertised URL actually works. Signed-off-by: Chris Evich <[email protected]>
Ref: containers#11165 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]>
Update test to confirm the negative-case, proving the `--privileged` "option is required" for this character device to be present in a container (including rootless). Signed-off-by: Chris Evich <[email protected]>
The `ls` command is not intended for this purpose and may behave in unexpected ways, leading to false positive or negative results. Update the tests to use the purpose built `test` command instead. Also added several *TODO* comments for possible future testing enhancements. Signed-off-by: Chris Evich <[email protected]>
This reverts commit 404d5ed. The replacement (updated) images include a fix for: containers/common#631 Also minor update to an unrelated FIXME comment. Signed-off-by: Chris Evich <[email protected]>
Ref: containers#10829 (comment) Signed-off-by: Chris Evich <[email protected]>
This becomes a problem on hosts with upgraded policies. Ref: containers#10522 Also, made a small change to compose-test setup to reduce runtime. Signed-off-by: Chris Evich <[email protected]>
These tests were originally enabled in a situation where CI provided false-positive results. Now that has been corrected, these tests all fail under a CGv1 container environment with the error: ``` Error: unable to load cgroup at /machine.slice/libpod-e4f...086.scope/libpod_parent/libpod-fbd...425: cgroup deleted ``` This commit simply disables the tests under this specific environment. Signed-off-by: Chris Evich <[email protected]>
1d70e88
to
a92441e
Compare
IMPORTANT: I'm okay if this PR merges before #10829 (to help with release timelines) however it makes me nervous. OTOH, the tests are passing, so 🤷♂️ |
LGTM |
/lgtm |
/hold cancel |
Backport of #10829 for the
v3.3
branchDepends on: #11164, #11166