Skip to content

Upgrade CRI-O to 1.20.0 #10478

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.

Sign up for GitHub

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

Jump to bottom
Closed
afbjorklund opened this issue Feb 14, 2021 · 3 comments
Closed

Upgrade CRI-O to 1.20.0 #10478

afbjorklund opened this issue Feb 14, 2021 · 3 comments
Assignees
@afbjorklund
Labels
co/runtime/crio CRIO related issues kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.18.0

Comments

@afbjorklund
Copy link
Collaborator

afbjorklund commented Feb 14, 2021 •
edited
Loading

Upgrade cri-o package, from 1.19.0 to 1.20.0

Tracker for #10476 (ISO) and #10477 (KIC)
@afbjorklund afbjorklund added this to the v1.18.0 milestone Feb 14, 2021
@afbjorklund afbjorklund added kind/feature Categorizes issue or PR as related to a new feature. co/runtime/crio CRIO related issues priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 14, 2021
@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Feb 20, 2021 •
edited
Loading

Ran into packaging issues, with storage.conf

See #10520 (package is: containers-common)

@medyagh medyagh mentioned this issue Feb 21, 2021
Merged
@medyagh
Copy link
Member

medyagh commented Feb 21, 2021

@afbjorklund could we close this ? since we merged #10477 ?
or do we need still update the VM too ?

@afbjorklund
Copy link
Collaborator Author

I think the VM was updated in #10476 was it not ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afbjorklund afbjorklund

Labels
co/runtime/crio CRIO related issues kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.18.0
Development

No branches or pull requests
2 participants
@medyagh @afbjorklund