-
Notifications
You must be signed in to change notification settings - Fork 1k
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
server: allow Bidirectional mounts that contain storage root #7408
server: allow Bidirectional mounts that contain storage root #7408
Conversation
Skipping CI for Draft Pull Request. |
cc @gnufied |
cc @harche |
/lgtm |
Since this was a regression. Can we get some unit or e2e/integration tests in crio itself to ensure we don't break again? |
previously we would never allow a container to get anything other than HostToContainer for something that contains the storage root. This breaks situations where the container wishes to update mount points within the container and see them propegated to the host. Instead, we should only override this if the mount is Private. Signed-off-by: Peter Hunt <pehunt@redhat.com>
7c0ad17
to
28c3955
Compare
good idea, added one for both cases this covers |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #7408 +/- ##
==========================================
+ Coverage 49.17% 49.31% +0.13%
==========================================
Files 138 138
Lines 15707 15774 +67
==========================================
+ Hits 7724 7779 +55
- Misses 7055 7058 +3
- Partials 928 937 +9 |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/retest
Is that still WIP? Looks like the bot did not remove the |
/cherry-pick release-1.28 |
@saschagrunert: once the present PR merges, I will cherry-pick it on top of release-1.28 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
1 similar comment
/retest |
Hm:
|
/retest-required |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, kwilczynski, saschagrunert 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 |
/retest-required |
@saschagrunert: new pull request created: #7456 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-1.27 |
@kwilczynski: #7408 failed to apply on top of branch "release-1.27":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
OK. Will backport manually. |
previously we would never allow a container to get anything other than HostToContainer for something that contains the storage root. This breaks situations where the container wishes to update mount points within the container and see them propegated to the host.
Instead, we should only override this if the mount is Private.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
fixes #7308
Special notes for your reviewer:
Does this PR introduce a user-facing change?