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-4.12] OCPBUGS-29278: crio: drop automatic image cleanup on upgrades #4178
[release-4.12] OCPBUGS-29278: crio: drop automatic image cleanup on upgrades #4178
Conversation
as it causes us to redundently pull images, and the kubelet should protect us from old images taking up too much disk space Signed-off-by: Peter Hunt <pehunt@redhat.com>
@openshift-cherrypick-robot: Jira Issue OCPBUGS-28740 has been cloned as Jira Issue OCPBUGS-29278. Will retitle bug to link to clone. 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 openshift-eng/jira-lifecycle-plugin repository. |
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-29278, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
@openshift-cherrypick-robot: 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. |
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.
/label backport-risk-assessed
Can we get this reviewed? I think this PR is needed to unblock 4.12 CI failures. |
The dependent bug https://issues.redhat.com//browse/OCPBUGS-28740 is still on QA and need to be verified, and this requires cherry-pick-approval after that I can /lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, sdodson, yuqi-zhang 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 |
/payload-job periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-azure-sdn-upgrade |
@jerpeter1: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0797a2e0-c9f6-11ee-98c7-bb04745b5aa6-0 |
/payload-aggregate periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-azure-sdn-upgrade 5 |
@sdodson: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1c8320b0-ca89-11ee-95e2-94f1efa0b9f1-0 |
/payload-aggregate periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-azure-sdn-upgrade 5 |
@sdodson: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4c4d7f70-cab6-11ee-9c37-937aa89bba96-0 |
/payload-aggregate periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-azure-sdn-upgrade 6 |
@sdodson: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/329d6210-cb3e-11ee-8329-87e43040954a-0 |
/jira refresh |
@sdodson: This pull request references Jira Issue OCPBUGS-29278, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (schoudha@redhat.com), skipping review request. 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 openshift-eng/jira-lifecycle-plugin repository. |
f9a34f9
into
openshift:release-4.12
@openshift-cherrypick-robot: Jira Issue OCPBUGS-29278: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-29278 has been moved to the MODIFIED state. 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 openshift-eng/jira-lifecycle-plugin repository. |
[ART PR BUILD NOTIFIER] This PR has been included in build ose-machine-config-operator-container-v4.12.0-202402141407.p0.gf9a34f9.assembly.stream.el8 for distgit ose-machine-config-operator. |
Fix included in accepted release 4.12.0-0.nightly-2024-02-14-150256 |
This is an automated cherry-pick of #4154
/assign sdodson