OCPBUGS-84643: Update RHCOS-release-4.22 bootimage metadata to 10.2.20260423-0 / 9.8.20260428-0

[coreosbot-releng]

Update data/data/coreos/coreos-rhel-10.json to 10.2.20260423-0

OCPBUGS-81187 - Multi-arch OpenShift 4.22.0-ec.4 and later vs. rpm-ostree "no signature exists"
OCPBUGS-83505 - Investigate RHCOS 9.8 initramfs size increase — risk to /boot on upgrading clusters

plume cosa2stream --target data/data/coreos/coreos-rhel-10.json                 \n    --distro rhcos --no-signatures --name rhel-10.2                     \n    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams  \n    x86_64=10.2.20260423-0                                       \n    aarch64=10.2.20260423-0                                      \n    s390x=10.2.20260423-0                                        \n    ppc64le=10.2.20260423-0

Update data/data/coreos/coreos-rhel-9.json to 9.8.20260428-0

OCPBUGS-81187 - Multi-arch OpenShift 4.22.0-ec.4 and later vs. rpm-ostree "no signature exists"
OCPBUGS-83505 - Investigate RHCOS 9.8 initramfs size increase — risk to /boot on upgrading clusters

plume cosa2stream --target data/data/coreos/coreos-rhel-9.json                 \n    --distro rhcos --no-signatures --name rhel-9.8                     \n    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams  \n    x86_64=9.8.20260428-0                                       \n    aarch64=9.8.20260428-0                                      \n    s390x=9.8.20260428-0                                        \n    ppc64le=9.8.20260428-0

[openshift-ci-robot]

@coreosbot-releng: This pull request references Jira Issue OCPBUGS-84643, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-84643 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Update data/data/coreos/coreos-rhel-10.json to 10.2.20260423-0

OCPBUGS-81187 - Multi-arch OpenShift 4.22.0-ec.4 and later vs. rpm-ostree "no signature exists"
OCPBUGS-83505 - Investigate RHCOS 9.8 initramfs size increase — risk to /boot on upgrading clusters

plume cosa2stream --target data/data/coreos/coreos-rhel-10.json                 \n    --distro rhcos --no-signatures --name rhel-10.2                     \n    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams  \n    x86_64=10.2.20260423-0                                       \n    aarch64=10.2.20260423-0                                      \n    s390x=10.2.20260423-0                                        \n    ppc64le=10.2.20260423-0

Update data/data/coreos/coreos-rhel-9.json to 9.8.20260428-0

OCPBUGS-81187 - Multi-arch OpenShift 4.22.0-ec.4 and later vs. rpm-ostree "no signature exists"
OCPBUGS-83505 - Investigate RHCOS 9.8 initramfs size increase — risk to /boot on upgrading clusters

plume cosa2stream --target data/data/coreos/coreos-rhel-9.json                 \n    --distro rhcos --no-signatures --name rhel-9.8                     \n    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams  \n    x86_64=9.8.20260428-0                                       \n    aarch64=9.8.20260428-0                                      \n    s390x=9.8.20260428-0                                        \n    ppc64le=9.8.20260428-0

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f011aa5c-5553-4a77-9dea-d01c702ff53b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jlebon for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• data/data/coreos/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @coreosbot-releng. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[sdodson]

/ok-to-test

[sdodson]

/test e2e-?

[sdodson]

/test e2e-azure-ovn e2e-gcp-ovn e2e-vsphere-ovn e2e-openstack-ovn

[openshift-ci]

@coreosbot-releng: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-openstack-ovn	c0f7ffc	link	true	/test e2e-openstack-ovn
ci/prow/e2e-gcp-ovn	c0f7ffc	link	true	/test e2e-gcp-ovn
ci/prow/e2e-vsphere-ovn	c0f7ffc	link	true	/test e2e-vsphere-ovn

Full PR test history. Your PR dashboard.

Details

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.

[openshift-ci-robot]

@coreosbot-releng: Jira Issue OCPBUGS-84643: All pull requests linked via external trackers have merged:

• openshift/installer#10523

Jira Issue OCPBUGS-84643 has been moved to the MODIFIED state.

Details

In response to this:

Update data/data/coreos/coreos-rhel-10.json to 10.2.20260423-0

OCPBUGS-81187 - Multi-arch OpenShift 4.22.0-ec.4 and later vs. rpm-ostree "no signature exists"
OCPBUGS-83505 - Investigate RHCOS 9.8 initramfs size increase — risk to /boot on upgrading clusters

plume cosa2stream --target data/data/coreos/coreos-rhel-10.json                 \n    --distro rhcos --no-signatures --name rhel-10.2                     \n    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams  \n    x86_64=10.2.20260423-0                                       \n    aarch64=10.2.20260423-0                                      \n    s390x=10.2.20260423-0                                        \n    ppc64le=10.2.20260423-0

Update data/data/coreos/coreos-rhel-9.json to 9.8.20260428-0

OCPBUGS-81187 - Multi-arch OpenShift 4.22.0-ec.4 and later vs. rpm-ostree "no signature exists"
OCPBUGS-83505 - Investigate RHCOS 9.8 initramfs size increase — risk to /boot on upgrading clusters

plume cosa2stream --target data/data/coreos/coreos-rhel-9.json                 \n    --distro rhcos --no-signatures --name rhel-9.8                     \n    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams  \n    x86_64=9.8.20260428-0                                       \n    aarch64=9.8.20260428-0                                      \n    s390x=9.8.20260428-0                                        \n    ppc64le=9.8.20260428-0

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.

[sdodson]

/cherry-pick main

[sdodson]

Same vsphere hot looping thing we saw last time and concluded it would go away once the sibling builds were updated, which doesn't happen in presubmits due to time required to produce a second build.

[openshift-cherrypick-robot]

@sdodson: new pull request created: #10524

Details

In response to this:

/cherry-pick main

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.