-
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
container: always check if mountpoint is mounted #20299
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe 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 |
Ephemeral COPR build failed. @containers/packit-build please check. |
705ebf3
to
ea50454
Compare
Thank you for persevering on this! Please don't lose your weekend over it, though. |
ea50454
to
0b21759
Compare
I keep seeing re-pushes but I don't see any difference in the new push. I think you're missing something? |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
0b21759
to
decb532
Compare
I wanted to test the PR better since it is a flake. I am analyzing the integration tests failures now |
when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process. To avoid this, always check if the mountpoint is really present before skipping the mount. [NO NEW TESTS NEEDED] Closes: containers#17042 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
decb532
to
8ac2aa7
Compare
Code LGTM |
I think we can ignore the RPM failures? |
/lgtm |
when running as a service, the c.state.Mounted flag could get out of sync if the container is cleaned up through the cleanup process.
To avoid this, always check if the mountpoint is really present before skipping the mount.
Closes: #17042
Does this PR introduce a user-facing change?