-
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
test: enable test_wait_next_exit #17854
test: enable test_wait_next_exit #17854
Conversation
Seems like it is still broken in CI. |
@matejvasek did you find time to analyze what's up? |
@vrothberg this test should be enabled once updated SELinux policy package is available in testing OS. The fix PR: containers/container-selinux#196 I find it odd it is not present, it's been quite a time since fix. |
@rhatdan @vrothberg the test runs on |
It has |
I can reproduce the issue locally with
|
@rhatdan ^^^ any idea what the problem could be? |
Before the error was different (different syscall was denied):
|
@rhatdan Maybe some other global SELinux policies changed? |
cc @edsantiago |
Whoosh. Way over my head, sorry. |
Can you get this to fail outside of the CI/CD system? |
What do I need to do to test this locally? |
# in podman project
python3 -m venv venv
source ./venv/bin/activate
pip3 install -r test/python/requirements.txt
export PODMAN=/path/to/podman
python -m unittest test.python.docker.compat.test_containers.TestContainers.test_wait_next_exit |
Sometimes the testing podman service hangs:
in such a case kill it manually. |
@rhatdan or just run a container with an image with 200k long labels an look into syslog. |
@rhatdan try this: |
@rhatdan have you managed to reproduce the issue? |
@rhatdan I don't know if it helps but: the AVC denied error happens when |
Before containers/container-selinux#196 the limit was just few 10k IIRC. |
The good news for me is the image we use has labels just very little bit above 100k so it working for my use-case. |
I really have no idea what is going on here. |
Something more from investigation: Larges message that can be sent to log is What is most likely happening:
The SELinux labels of the temp file |
@rhatdan @edsantiago I added some new findings above. |
simple reproducer: var err error
msgLen := 212_940 + 1
data := make([]byte, msgLen)
for i := range data {
data[i] = '0'
}
err = journal.Send(string(data[:msgLen]), journal.PriInfo, nil)
if err != nil {
t.Fatal(err)
} don't forget to set |
d87e3ab
to
1f58b64
Compare
container-selinux-2.209.0 should fix this. |
There's a new CI VM build in progress, expected for next week maybe. f37 includes container-selinux-209 but unfortunately f36 does not |
The |
6f6c80b
to
eb241b6
Compare
@matejvasek re-pushing isn't going to do any good if you don't rebase. The magic you need is in |
Signed-off-by: Matej Vasek <[email protected]>
eb241b6
to
d286564
Compare
@rhatdan @edsantiago Thanks. It should be all right now. |
I think this is the test in question?. It passed (all tests pass), and shows /approve @rhatdan PTAL. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago, matejvasek 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 |
/lgtm |
Does this PR introduce a user-facing change?