-
Notifications
You must be signed in to change notification settings - Fork 462
Bug 1826896: [release-4.4] crio: set version-file{,-persist} correctly #1679
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 1826896: [release-4.4] crio: set version-file{,-persist} correctly #1679
Conversation
with a new version of cri-o, we are going to cleanup containers when a node reboots (which we detect when a tmpfs file is removed), and cleanup images when a node upgraded (which we detect how we used to: persistent version file out of date) This PR changes where cri-o looks for those files. These match the upstream defaults, so when we move to drop in files, we won't need to specify these Signed-off-by: Peter Hunt <[email protected]>
|
@haircommander: This pull request references Bugzilla bug 1826896, which is invalid:
Comment 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. |
|
/hold needs cri-o/cri-o#3635 integrated into 4.4 first |
|
@mrunalp PTAL |
|
LGTM |
kikisdeliveryservice
left a comment
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.
approving sthis but will need lgtm and passing ci via a new rpm (which is all in progress)
|
Updated cri-o will be pinned in the boot image via openshift/installer#3508 |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, kikisdeliveryservice, mrunalp The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
Clearing containers on reboot makes total sense for cri-o. But...clearing images conflicts with the messaging in openshift/machine-api-operator#565 to some degree. The story still holds for minor updates of course. Ideally at some point we have rigorous enough testing for the containers/image layer across upgrades that we don't need to do this (or, we only do it for actually breaking changes to the image store). |
Yes, agree with this 👍 With rigorous enough testing we can rely on the kubelet to gc older images. |
|
used old images /retest |
|
@haircommander: This pull request references Bugzilla bug 1826896, which is invalid:
Comment 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. |
|
@haircommander: This pull request references Bugzilla bug 1826896, which is invalid:
Comment 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. |
|
/test e2e-gcp-upgrade |
|
/test e2e-aws-scaleup-rhel7 |
|
waiting on e2e-gcp-op & e2e-gcp-upgrade to finish.. rhel7 job (not reqd) seems to be going through something today. ¯_(ツ)_/¯ |
|
/skip |
|
@haircommander: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. |
|
/retest |
|
@haircommander: All pull requests linked via external trackers have merged: cri-o/cri-o#3635, openshift/installer#3508, openshift/machine-config-operator#1679. Bugzilla bug 1826896 has been moved to the MODIFIED state. 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 I did
with a new version of cri-o, we are going to cleanup containers when a node reboots (which we detect when a tmpfs file is removed), and cleanup images when a node upgraded (which we detect how we used to: persistent version file out of date)
This PR changes where cri-o looks for those files. These match the upstream defaults, so when we move to drop in files, we won't need to specify these
- How to verify it
containers are cleared on node reboot, images are cleared when we bump a cri-o minor version (1.17->1.18)
- Description for the changelog