-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[1.22] Backport crio storage wipe #6420
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
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: wgahnagl The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
c7fe9f9 to
9d25aaa
Compare
Signed-off-by: Peter Hunt <[email protected]>
9d25aaa to
851176c
Compare
|
I think you need to run |
f1b55ff to
79a2a07
Compare
|
/retest |
1 similar comment
|
/retest |
Signed-off-by: Peter Hunt <[email protected]>
79a2a07 to
7f29fb1
Compare
|
/retest |
|
A friendly reminder that this PR had no activity for 30 days. |
|
@cri-o/cri-o-maintainers As a follow-up for #6544 (comment), does it makes sense to close this PR as 1.22 is out of support ? |
|
we still have downstream obligations that motivate this change. We just probably won't package it upstream |
|
/close to leverage #6612 |
|
@jrvaldes: Closed this PR. DetailsIn 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. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
cherry-pick of #6022
Which issue(s) this PR fixes:
https://issues.redhat.com/browse/OCPBUGS-3708
Special notes for your reviewer:
Does this PR introduce a user-facing change?