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
Bug 1981187: Fix dangling volumes vsphere #890
Bug 1981187: Fix dangling volumes vsphere #890
Conversation
Make inability to fetch canonicalPath non-fatal error Throw error if we can't fetch canonicalPath on attach
@gnufied: Bugzilla bug 1981187 is in a bug group that is not in the allowed groups for this repo.
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. |
@gnufied: the contents of this pull request could be automatically validated. The following commits are valid:
|
/bugzilla refresh |
@gnufied: Bugzilla bug 1981187 is in a bug group that is not in the allowed groups for this repo.
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 |
/retest |
/retest |
1 similar comment
/retest |
/bugzilla refresh |
@gnufied: Bugzilla bug 1981187 is in a bug group that is not in the allowed groups for this repo.
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. |
I don't see the 1.19 cherrypicks for these upstream.
Comment kubernetes#96534 (comment) suggests a willingness to merge the upstream if they can be made to function in 1.19. |
I now see kubernetes#104485 and kubernetes#104485 just waiting on the patchmanager. You often have better luck getting them on slack. Looks like just two more: kubernetes#96224 and kubernetes#96689 |
@deads2k yep. though they are dependent PRs, so I will have to wait for kubernetes#104485 before I can open another set of cherry-picks. |
@deads2k so looks like kubernetes#104485 got merged. Since there are PR dependencies I have opened kubernetes#104910 against 1.20 and then I will have to open another PR against 1.19 |
Also backport for 1.19 - kubernetes#104912 |
@gnufied: the contents of this pull request could be automatically validated. The following commits are valid:
|
@gnufied: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@damemi fyi, since you're doing 4.6 bump |
/lgtm |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gnufied, jsafrane The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
this just merged, so we'll get it for free with 1.19.15 release soon |
@soltysh FYI this is stil not merged and available in latest OCP-4.6. |
it'll be part of the next rounds of k8s bumps, iirc |
/close |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1981187
cc @openshift/sig-storage
Note to reviewers - this issue is already fixed in 4.7 onwards and hence does not require backports to those versions.
Pending backports in upstream:
kubernetes#104912 (against 1.19)
kubernetes#104910 (against 1.20)