Skip to content
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

[release-1.27] server: allow Bidirectional mounts that contain storage root #7457

Conversation

kwilczynski
Copy link
Member

This is a manual cherry-pick of #7076 and #7408

/assign kwilczynski

- Set mount type HostToContainer for mounts that include container storage root
- Fix a bug where CRI-O would override a Bidirectional mount in favor of a HostToContainer if the mount contained the host's container storage

harche and others added 2 commits October 31, 2023 20:28
…age root

Signed-off-by: Harshal Patil <harpatil@redhat.com>
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>
@openshift-ci-robot
Copy link

@kwilczynski: This pull request explicitly references no jira issue.

In response to this:

This is a manual cherry-pick of #7076 and #7408

/assign kwilczynski

- Set mount type HostToContainer for mounts that include container storage root
- Fix a bug where CRI-O would override a Bidirectional mount in favor of a HostToContainer if the mount contained the host's container storage

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 31, 2023
@openshift-ci openshift-ci bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Oct 31, 2023
Copy link

codecov bot commented Oct 31, 2023

Codecov Report

Merging #7457 (dde9ff5) into release-1.27 (9b9c375) will increase coverage by 0.01%.
Report is 2 commits behind head on release-1.27.
The diff coverage is 72.72%.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-1.27    #7457      +/-   ##
================================================
+ Coverage         49.30%   49.31%   +0.01%     
================================================
  Files               128      128              
  Lines             15187    15196       +9     
================================================
+ Hits               7488     7494       +6     
- Misses             6801     6803       +2     
- Partials            898      899       +1     

@kwilczynski
Copy link
Member Author

/lgtm

Copy link
Contributor

openshift-ci bot commented Nov 1, 2023

@kwilczynski: you cannot LGTM your own PR.

In response to this:

/lgtm

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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 1, 2023
Copy link
Contributor

openshift-ci bot commented Nov 1, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 1, 2023
@openshift-ci openshift-ci bot merged commit 956c5f7 into cri-o:release-1.27 Nov 1, 2023
38 of 44 checks passed
@kwilczynski kwilczynski deleted the feature/cherry-pick-bb98e2b2a-28c395533-to-release-1.27 branch November 1, 2023 11:05
@haircommander
Copy link
Member

hm why did we backport this? was someone asking for this behavior? I worry about having introduced more issues (even past the one that is now fixed) and I'm not sure we should introduce such instability into this branch

@kwilczynski
Copy link
Member Author

Hi @haircommander,

hm why did we backport this? was someone asking for this behavior? I worry about having introduced more issues (even past the one that is now fixed) and I'm not sure we should introduce such instability into this branch

What do you mean when you say "instability"? Do you foresee issues?

I am asking as we backported this to release 1.28, and we are about to cut a 1.28.2 release.

Similarly, with 1.27.2 - it was with anticipation of this new release and the fact that we made a backport to a different release branch I decided to backport this fix. Both are our active releases, and this fixes issues with some CSI that people use.

If we weren't entirely sure about this, why backport to 1.28 and not just leave it on the main branch?

Nevertheless, we can revert before you cut the 1.27.2 release. 😄

@haircommander
Copy link
Member

FWIW: the initial commit here is kind of a feature. It fixes an issue when users mount /host and aren't able to see updates to /var/lib/containers. that said, I think it's fine. let's leave it for now

@kwilczynski kwilczynski changed the title [release-1.27] NO-ISSUE: server: allow Bidirectional mounts that contain storage root [release-1.27] server: allow Bidirectional mounts that contain storage root Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants