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
MGMT-15808: change base image to stream9 #5497
MGMT-15808: change base image to stream9 #5497
Conversation
Now that D/S building system fully supports RHEL-9 base images (and allows easy installation of nmstate and other libs that were previously unsupported) we can move U/S to stream9 and D/S to ubi9-minimal. It doesn't seem possible to easily use ubi9-minimal U/S, because installation of nmstate packages (and libvirt-libs) either requires entitlements running on a RHEL node, or maybe alternatively an access to RedHat's internal network (which can be a major problem for development U/S).
@osherdp: This pull request references MGMT-15808 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 task to target the "4.15.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 kubernetes/test-infra repository. |
Skipping CI for Draft Pull Request. |
/test all |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5497 +/- ##
==========================================
+ Coverage 67.64% 67.87% +0.22%
==========================================
Files 232 232
Lines 34099 34370 +271
==========================================
+ Hits 23065 23327 +262
- Misses 8971 8979 +8
- Partials 2063 2064 +1 |
/retest |
/hold |
/test e2e-agent-compact-ipv4 |
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.
/lgtm
Should this also be changed to RHEL9? not sure if it belongs in this PR.
|
I guess it can be done in a followup PR, not sure what's the schedule for ABI for migrating to rhel9 |
/override ci/prow/e2e-agent-compact-ipv4 |
/unhold |
@osherdp: Overrode contexts on behalf of osherdp: ci/prow/e2e-agent-compact-ipv4 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/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adriengentil, nmagnezi, osherdp 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 |
@osherdp: 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/test-infra repository. I understand the commands that are listed here. |
Now that D/S building system fully supports RHEL-9 base images (and allows easy installation of nmstate and other libs that were previously unsupported) we can move U/S to stream9 and D/S to ubi9-minimal. It doesn't seem possible to easily use ubi9-minimal U/S, because installation of nmstate packages (and libvirt-libs) either requires entitlements running on a RHEL node, or maybe alternatively an access to RedHat's internal network (which can be a major problem for development U/S).
Now that D/S building system fully supports RHEL-9 base images (and allows easy installation of nmstate and other libs that were previously unsupported) we can move U/S to stream9 and D/S to ubi9-minimal.
It doesn't seem possible to easily use ubi9-minimal U/S, because installation of nmstate packages (and libvirt-libs) either requires entitlements running on a RHEL node, or maybe alternatively an access to RedHat's internal network (which can be a major problem for development U/S).
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist