-
Notifications
You must be signed in to change notification settings - Fork 107
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
COS-2959: Add rhel-9.6 and ocp-rhel-9.6 variants #1629
COS-2959: Add rhel-9.6 and ocp-rhel-9.6 variants #1629
Conversation
0e00216
to
70ea386
Compare
manifest-rhel-9.6.yaml
Outdated
cat > /usr/lib/os-release <<EOF | ||
NAME="Red Hat Enterprise Linux" | ||
VERSION="9.6 (Plow)" | ||
ID="rhel" | ||
ID_LIKE="fedora" | ||
VERSION="${OSTREE_VERSION}" | ||
VARIANT="CoreOS" | ||
VARIANT_ID=coreos | ||
VERSION_ID="9.6" | ||
PLATFORM_ID="platform:el9" | ||
PRETTY_NAME="${NAME} CoreOS ${OSTREE_VERSION}" | ||
ANSI_COLOR="0;31" | ||
LOGO="fedora-logo-icon" | ||
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::coreos" | ||
HOME_URL="https://www.redhat.com/" | ||
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9" | ||
BUG_REPORT_URL="https://issues.redhat.com/" | ||
|
||
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9" | ||
REDHAT_BUGZILLA_PRODUCT_VERSION=9.6 | ||
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" | ||
REDHAT_SUPPORT_PRODUCT_VERSION="9.6" | ||
EOF |
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.
Can you show the resulting /etc/os-release
file in the built container image/VM? Compare to https://gist.github.com/jlebon/908e45c42ce9e365fb83d7470cbbb40c for how it currently looks for rhel-9.4
.
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.
I just updated to have something that matches :
NAME="Red Hat Enterprise Linux CoreOS"
VERSION="9.6.202410031540-0 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION="9.6.202410031540-0"
VARIANT="CoreOS"
VARIANT_ID=coreos
VERSION_ID="9.6"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux CoreOS 9.6.202410031540-0 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9"
BUG_REPORT_URL="https://issues.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.6"
OSTREE_VERSION="9.6.202410031540-0"
70ea386
to
4707c1a
Compare
/retest |
4707c1a
to
1176c70
Compare
/hold |
50c78e2
to
96503ef
Compare
ca926b1
to
810c9af
Compare
@jbtrystram: This pull request references COS-2959 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 story to target the "4.18.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. |
/unhold |
Preparation work to update openshift/release jobs to build rhel 9.6 and c10s. Needs to be merged before openshift#1629 and openshift#1498
is the intention to squash these commits when ready to merge? |
extensions-ocp-rhel-9.6.yaml
Outdated
@@ -0,0 +1 @@ | |||
extensions-ocp-rhel-9.4.yaml |
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.
if this is going to be a symlink to extensions-ocp-rhel-9.4.yaml
(which is itself a symlink to extensions-rhel-9.4.yaml
) then why create extensions-rhel-9.6.yaml
at all?
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.
That's a mistake, it should link to extensions-rhel-9.6.yaml
extensions-rhel-9.6.yaml
Outdated
# https://github.com/openshift/enhancements/blob/master/enhancements/sandboxed-containers/sandboxed-containers-tech-preview.md | ||
# GRPA-3123 | ||
# - kata-containers | ||
# s390x builds not available in c9s |
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.
# s390x builds not available in c9s
but what change did you make because of that fact? the following section matches exactly extensions-rhel-9.4.yaml
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.
Because s390x builds are not available in c9s we have to pull from rhel 9.4, so yeah, it's identical to the 9.4 file
extensions-rhel-9.6.yaml
Outdated
- aarch64 | ||
repos: | ||
- rhel-9.4-server-ose-4.18 | ||
- rhel-9.4-appstream |
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.
Why did we add rhel-9.4-appstream
here when compared to the same section in extensions-rhel-9.4.yaml
?
# info in a post-process script | ||
- centos-stream-release | ||
|
||
# Fake out RHEL version in the os-release while waiting for RHEL-9.6 release. |
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.
should we just be find/replace 9.4
with 9.6
in the os-release
here? i.e. in manifest-rhel-9.4.yaml
there is no postprocess of os-release
that is done now (since 4e09d27) so we shouldn't need to replace the whole thing?
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.
should we just be find/replace 9.4 with 9.6 in the os-release here?
Doing that would require installing redhat-release
from the rhel 9.4 repos. That release file comes from centos-strea-release
. I tried to do that, as that would make things simpler here but then conflicts with centos-stream-release
which is required to get the RPM repository files and GPG keys and causes issues when trying to build the extensions container (which needs to downloads RPMs)
07df0b6
to
052da93
Compare
I was thinking of making several commits so the denylists changes would be easier to revert but since i'll have to do changes in the manifest anyway i'll do it in one go I suppose |
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
052da93
to
84771a2
Compare
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.
One nit and one fix needed
manifest-ocp-rhel-9.6.yaml
Outdated
@@ -0,0 +1,111 @@ | |||
# Manifest for OCP node based on RHEL 9.4 |
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.
# Manifest for OCP node based on RHEL 9.4 | |
# Manifest for OCP node based on RHEL 9.6 |
Right now these are pure centOS Stream 9 builds with a spoofed `os-release` file. For the ocp variant, pull the packages from the 9.4-4.18 repos. https://issues.redhat.com/browse/COS-2959 [rhel-9.6] denylist expected failing testsas it's a fake rhel-9.6 This 9.6 rhel version is faked from centOS stream 9 so those tests are expected to fail. See openshift#1635 denylist: exclude secureboot tests for rhel 9.6 secureboot does not work on c9s for now, so as this rhel 9.6 is just c9s, it won't either. denylist those tests until beta. This is the same as openshift@c95eedc
84771a2
to
c14de7e
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dustymabe, jbtrystram, travier 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 |
@jbtrystram: 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. |
Right now these are pure centOS Stream 9 builds with a spoofed
os-release
file.For the ocp variant, pull the packages from the 9.4-4.18 repos.
https://issues.redhat.com/browse/COS-2959