-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
UPSTREAM: 49118: Allow unmounting bind-mounted directories. #15294
UPSTREAM: 49118: Allow unmounting bind-mounted directories. #15294
Conversation
Cc @simo5, @openshift/security. |
@adelton When you're editing files inside |
@openshift/storage |
I see that Travis already has failing the build with the error about that:
Unfortunately it doesn't mention what are these conventions. Here is the link that I'm using: origin/tools/rebasehelpers/commitchecker/validate.go Lines 19 to 38 in 7d661a2
|
See https://github.com/openshift/origin/blob/master/HACKING.md#using-hackcherry-pick |
this should be opened upstream for review and approval first. we only pick changes into origin if they are fixing release-blocking bugs, otherwise we wait to pick up the kube level with upstream improvements |
Filed upstream now: kubernetes/kubernetes#49118. Let's see. |
@adelton, please update the commit message. https://github.com/openshift/origin/blob/master/HACKING.md#using-hackcherry-pick says: All upstream commits should have a commit message where the first line is: Check git log for examples. |
The kubernetes/kubernetes#49118 was merged. Do we want to get that change in to OpenShift Origin now, making testing with bind-mounted directories (and files) easier, or wait for rebase and drop this pull request? |
For bind-mounted directories, the isNotMounted which calls IsLikelyNotMountPoint fails because the filesystem of the mounted location and the parent directory are the same. Addressing: unmounter.go:59] Warning: Path: /path/.../test-dir already unmounted
Updated commit message, rebased on master -> 139e0d5. |
[test] |
Evaluated for origin test up to 139e0d5 |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/3477/) (Base Commit: 970dc61) (PR Branch Commit: 139e0d5) |
[merge] |
continuous-integration/openshift-jenkins/merge Waiting: You are in the build queue at position: 2 |
Evaluated for origin merge up to 139e0d5 |
/approve no-issue |
What can be done to get this merged? That "Submit Queue" check does not really give much clue about what it feels is wrong with the change. |
/test all |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adelton, jsafrane The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test ci/openshift-jenkins/extended_templates |
/test extended_templates |
/test all [submit-queue is verifying that this PR is safe to merge] |
/retest |
1 similar comment
/retest |
Those https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/3880/ failures don't seem like something this patch could have caused. What is the best way to report / escalate those, @jsafrane ? |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
/test all [submit-queue is verifying that this PR is safe to merge] |
/retest |
1 similar comment
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
For files, we cannot use
path/..
;we could use
filepath.Dir
but for bind-mounted,isNotMounted
which calls
IsLikelyNotMountPoint
would not work anyway.Let's just have the driver do the work.
Addressing