Skip to content

OCPBUGS-98982: Update RHCOS-release-4.22 bootimage metadata to 9.8.20260715-1 / 10.2.20260715-0#10692

Merged
openshift-merge-bot[bot] merged 2 commits into
openshift:release-4.22from
coreosbot-releng:bootimage-bump-9.8.20260715-1
Jul 17, 2026
Merged

OCPBUGS-98982: Update RHCOS-release-4.22 bootimage metadata to 9.8.20260715-1 / 10.2.20260715-0#10692
openshift-merge-bot[bot] merged 2 commits into
openshift:release-4.22from
coreosbot-releng:bootimage-bump-9.8.20260715-1

Conversation

@coreosbot-releng

Copy link
Copy Markdown

Update data/data/coreos/coreos-rhel-9.json to 9.8.20260715-1

Bumps the boot image to 4.22 to support coreos/coreos-assembler#4594.
This updates OSBuild to generate "nvidiabluefield" BFB images with GRUB shims instead of kernels, enabling secure boot for their upcoming GA release.

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.20260715-1                                       \n    aarch64=9.8.20260715-1                                      \n    s390x=9.8.20260715-1                                        \n    ppc64le=9.8.20260715-1

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

Bumps the boot image to 4.22 to support coreos/coreos-assembler#4594.
This updates OSBuild to generate "nvidiabluefield" BFB images with GRUB shims instead of kernels, enabling secure boot for their upcoming GA release.

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.20260715-0                                       \n    aarch64=10.2.20260715-0                                      \n    s390x=10.2.20260715-0                                        \n    ppc64le=10.2.20260715-0

CoreOS Bot added 2 commits July 16, 2026 23:16
Bumps the boot image to 4.22 to support coreos/coreos-assembler#4594.
This updates OSBuild to generate "nvidiabluefield" BFB images with GRUB shims instead of kernels, enabling secure boot for their upcoming GA release.

```
plume cosa2stream --target data/data/coreos/coreos-rhel-9.json                 \
    --distro rhcos --no-signatures --name rhel-9.8                     \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams  \
    x86_64=9.8.20260715-1                                       \
    aarch64=9.8.20260715-1                                      \
    s390x=9.8.20260715-1                                        \
    ppc64le=9.8.20260715-1
```
Bumps the boot image to 4.22 to support coreos/coreos-assembler#4594.
This updates OSBuild to generate "nvidiabluefield" BFB images with GRUB shims instead of kernels, enabling secure boot for their upcoming GA release.

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

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@aaradhak

Copy link
Copy Markdown
Contributor

/pipeline required

@aaradhak

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 16, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@coreosbot-releng: This pull request references Jira Issue OCPBUGS-98982, 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-98982 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-9.json to 9.8.20260715-1

Bumps the boot image to 4.22 to support coreos/coreos-assembler#4594.
This updates OSBuild to generate "nvidiabluefield" BFB images with GRUB shims instead of kernels, enabling secure boot for their upcoming GA release.

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.20260715-1                                       \n    aarch64=9.8.20260715-1                                      \n    s390x=9.8.20260715-1                                        \n    ppc64le=9.8.20260715-1

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

Bumps the boot image to 4.22 to support coreos/coreos-assembler#4594.
This updates OSBuild to generate "nvidiabluefield" BFB images with GRUB shims instead of kernels, enabling secure boot for their upcoming GA release.

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.20260715-0                                       \n    aarch64=10.2.20260715-0                                      \n    s390x=10.2.20260715-0                                        \n    ppc64le=10.2.20260715-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.

@tlbueno

tlbueno commented Jul 17, 2026

Copy link
Copy Markdown
Member

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 17, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-azure-nat-gateway-single-zone

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn-fips
/test e2e-aws-ovn

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 17, 2026
@aaradhak

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@aaradhak: This pull request references Jira Issue OCPBUGS-98982, which is invalid:

  • expected Jira Issue OCPBUGS-98982 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.

Details

In response to this:

/jira refresh

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.

@marmijo marmijo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aaradhak, marmijo, tlbueno

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

The pull request process is described here

Details 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

@aaradhak

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@aaradhak: This pull request references Jira Issue OCPBUGS-98982, which is invalid:

  • expected Jira Issue OCPBUGS-98982 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.

Details

In response to this:

/jira refresh

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.

@aaradhak

Copy link
Copy Markdown
Contributor

@sdodson Can I get the backport-risk-assessed label for this PR?

@aaradhak

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@aaradhak: This pull request references Jira Issue OCPBUGS-98982, which is invalid:

  • expected Jira Issue OCPBUGS-98982 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.

Details

In response to this:

/jira refresh

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 sdodson added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 17, 2026
@sdodson

sdodson commented Jul 17, 2026

Copy link
Copy Markdown
Member

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 17, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sdodson: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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-merge-bot
openshift-merge-bot Bot merged commit d2c0cfc into openshift:release-4.22 Jul 17, 2026
17 of 18 checks passed
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@coreosbot-releng: Jira Issue Verification Checks: Jira Issue OCPBUGS-98982
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-98982 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Update data/data/coreos/coreos-rhel-9.json to 9.8.20260715-1

Bumps the boot image to 4.22 to support coreos/coreos-assembler#4594.
This updates OSBuild to generate "nvidiabluefield" BFB images with GRUB shims instead of kernels, enabling secure boot for their upcoming GA release.

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.20260715-1                                       \n    aarch64=9.8.20260715-1                                      \n    s390x=9.8.20260715-1                                        \n    ppc64le=9.8.20260715-1

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

Bumps the boot image to 4.22 to support coreos/coreos-assembler#4594.
This updates OSBuild to generate "nvidiabluefield" BFB images with GRUB shims instead of kernels, enabling secure boot for their upcoming GA release.

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.20260715-0                                       \n    aarch64=10.2.20260715-0                                      \n    s390x=10.2.20260715-0                                        \n    ppc64le=10.2.20260715-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.

@openshift-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in release 4.22.0-0.nightly-2026-07-18-105106

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants