Skip to content
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-2370: Changes to allow MicroShift 4.16 to build on RHEL 9.4 Beta #3220

Merged
merged 7 commits into from
Apr 9, 2024

Conversation

dhensel-rh
Copy link
Contributor

@dhensel-rh dhensel-rh commented Apr 5, 2024

Which issue(s) this PR addresses:

Closes #USHIFT-2370

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 5, 2024

@dhensel-rh: This pull request references USHIFT-2370 which is a valid jira issue.

In response to this:

Which issue(s) this PR addresses:

Closes #USHIFT-2370

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-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 5, 2024
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 5, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 5, 2024

@dhensel-rh: This pull request references USHIFT-2370 which is a valid jira issue.

In response to this:

Which issue(s) this PR addresses:

Closes #USHIFT-2370

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.

Copy link
Contributor

openshift-ci bot commented Apr 5, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@dhensel-rh dhensel-rh marked this pull request as ready for review April 5, 2024 16:31
@dhensel-rh dhensel-rh marked this pull request as draft April 5, 2024 16:31
scripts/devenv-builder/configure-vm.sh Show resolved Hide resolved
@@ -23,6 +23,13 @@ fi
createrepo yum-utils selinux-policy-devel jq wget lorax rpm-build \
containernetworking-plugins expect"

VID=$(source /etc/os-release && echo "${VERSION_ID}")
if { [[ "${VID}" == "9.4" ]] && grep -qE 'Red Hat Enterprise Linux.*Beta' /etc/redhat-release; }; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know we're not going to see a RHEL 9.5 for a minute, but could this be generalized so it's not something we have to continually update? Maybe we could detect if it's a beta version?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we should probably change it to be more generic, something like the following

if grep -qE 'Red Hat Enterprise Linux.*Beta' /etc/redhat-release; then
   VID=$(source /etc/os-release && echo "${VERSION_ID}")
   sudo sed -i "s,dist/rhel9/${VID},beta/rhel9/9,g" /usr/share/osbuild-composer/repositories/rhel-${VID}.json
fi

@dhensel-rh dhensel-rh marked this pull request as ready for review April 8, 2024 11:14
@dhensel-rh dhensel-rh changed the title [WIP] USHIFT-2370: Changes to allow MicroShift 4.16 to build on RHEL 9.4 Beta USHIFT-2370: Changes to allow MicroShift 4.16 to build on RHEL 9.4 Beta Apr 8, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 8, 2024
@dhensel-rh
Copy link
Contributor Author

/retest

@dhensel-rh
Copy link
Contributor Author

/retest

@dhensel-rh
Copy link
Contributor Author

/retest

@copejon
Copy link
Contributor

copejon commented Apr 9, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 9, 2024
Copy link
Contributor

openshift-ci bot commented Apr 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, dhensel-rh

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 9, 2024
Copy link
Contributor

openshift-ci bot commented Apr 9, 2024

@dhensel-rh: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 4012491 into openshift:main Apr 9, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants