NO-JIRA: [RHCOS10] Test existing UBI9 base images on RHCOS10 nodes (no changes)#107
NO-JIRA: [RHCOS10] Test existing UBI9 base images on RHCOS10 nodes (no changes)#107PillaiManish wants to merge 1 commit intoopenshift:mainfrom
Conversation
Documents the test plan for validating existing OCP/RHEL9-based images on an RHCOS10 cluster before migrating to UBI10 (PR2). Made-with: Cursor
openshift-ci-robot
added
the
jira/valid-reference
|
@PillaiManish: This pull request explicitly references no jira issue. DetailsIn 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. |
WalkthroughA new documentation file was added describing a baseline CI compatibility smoke test for running existing UBI9/RHEL9-based container images on an RHCOS10 cluster, including test specifications, expected outcomes, and a reference to a subsequent migration pull request. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: PillaiManish The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/rhcos10-ubi9-compat-test.md`:
- Line 37: The markdown link "[rhcos10-ubi10-migration](../)" is pointing to the
parent directory instead of a specific PR or doc; update the link target for
clarity by either replacing the relative "../" target with the full URL or
issue/PR number (e.g., the PR URL or "#<PR_NUMBER>") or, if the PR doesn't exist
yet, remove the markdown link and make it plain text "PR2
(rhcos10-ubi10-migration)"; locate and edit the link text
"[rhcos10-ubi10-migration](../)" in docs/rhcos10-ubi9-compat-test.md to apply
the chosen fix.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 2d4405b7-67a0-469a-8492-1665441b867c
📒 Files selected for processing (1)
docs/rhcos10-ubi9-compat-test.md
|
|
||
| ## Follow-up | ||
|
|
||
| If CI passes → PR2 ([rhcos10-ubi10-migration](../)) migrates all base images from |
There was a problem hiding this comment.
Fix the broken link to the follow-up PR.
The link [rhcos10-ubi10-migration](../) points only to the parent directory instead of a specific PR or document. This will be confusing for readers trying to navigate to the referenced migration work.
Consider one of these options:
- Link to a specific issue/PR number if it exists (e.g.,
#108or full URL) - Remove the link and use plain text if the PR hasn't been created yet:
PR2 (rhcos10-ubi10-migration) - Link to a tracking issue or epic that will contain the migration PR
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/rhcos10-ubi9-compat-test.md` at line 37, The markdown link
"[rhcos10-ubi10-migration](../)" is pointing to the parent directory instead of
a specific PR or doc; update the link target for clarity by either replacing the
relative "../" target with the full URL or issue/PR number (e.g., the PR URL or
"#<PR_NUMBER>") or, if the PR doesn't exist yet, remove the markdown link and
make it plain text "PR2 (rhcos10-ubi10-migration)"; locate and edit the link
text "[rhcos10-ubi10-migration](../)" in docs/rhcos10-ubi9-compat-test.md to
apply the chosen fix.
|
/test operator-e2e-azure-rhcos10-fips operator-e2e-azure-rhcos10 |
|
/retest |
|
@PillaiManish: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
2 participants
Summary
Validate that the existing UBI9-based images run correctly on RHCOS10 cluster nodes without any changes.
RHCOS10 ships with RHEL10 as its host OS. This PR triggers CI against an RHCOS10 cluster to confirm
UBI9 containers remain compatible before committing to a base image migration.
No Dockerfile changes. This is a baseline/smoke test only.
Follow-up
If CI passes → PR2 migrates all base images from UBI9 to UBI10.