-
Notifications
You must be signed in to change notification settings - Fork 216
USHIFT-5352: Use EUS bootc base images and prevent unintended OS version upgrade #4531
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
USHIFT-5352: Use EUS bootc base images and prevent unintended OS version upgrade #4531
Conversation
@ggiguash: This pull request references USHIFT-5352 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set. 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. |
Skipping CI for Draft Pull Request. |
Transient subscription management issues
/test e2e-aws-tests-bootc |
/cherry-pick release-4.18 |
@ggiguash: once the present PR merges, I will cherry-pick it on top of 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-sigs/prow repository. |
@@ -9,6 +9,8 @@ FROM ${BASE_IMAGE_URL}:${BASE_IMAGE_TAG} | |||
|
|||
ARG DNF_OPTIONS | |||
|
|||
# Do not run 'dnf upgrade' command to avoid overrides of the base | |||
# images specified by the container image build pipelines. |
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.
Is this the best advice we can give? Are those images rebuilt daily so we don't need to upgrade the packages?
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.
It's not an advice, this is a requirement that comes from the ART pipelines. They are responsible for selecting the base image.
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.
It goes back to the comment in the beginning of this Containerfile. It's crafted for ART pipeline requirements.
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.
Ack, I didn't see the comment at the top of the file, so I assumed this is an example for the user (just like the blueprint example in release-info rpm)
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ggiguash, pmtk 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 |
@ggiguash: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
@ggiguash: #4531 failed to apply on top of branch "release-4.18":
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-sigs/prow repository. |
No description provided.