Skip to content

Conversation

@tlbueno
Copy link
Member

@tlbueno tlbueno commented Dec 29, 2025

OCPBUGS-66355: Update the RHCOS 4.21 bootimage metadata to 9.6.20251212-1
The changes done here will update the RHCOS 4.21 bootimage metadata and
address the following issues:

OCPBUGS-61669: [4.21] coreos-boot-disk link not working with multipath on early boot
OCPBUGS-65669: Cannot use auto-forward kargs (like ip=) with coreos-installer (iso|pxe) customize
OCPBUGS-65684: Ignition fails with crypto/ecdh: invalid random source in FIPS 140-only mode
OCPBUGS-68354: Using multipath on the sysroot will fail to boot if less than 2 paths are present

This change was generated using:

plume cosa2stream \
    --target data/data/coreos/rhcos.json \
    --distro rhcos \
    --no-signatures \
    --name rhel-9.6 \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=9.6.20251212-1        \
    aarch64=9.6.20251212-1       \
    s390x=9.6.20251212-1         \
    ppc64le=9.6.20251212-1

…12-1

The changes done here will update the RHCOS 4.21 bootimage metadata and
address the following issues:

OCPBUGS-61669: [4.21] coreos-boot-disk link not working with multipath on early boot
OCPBUGS-65669: Cannot use auto-forward kargs (like ip=) with coreos-installer (iso|pxe) customize
OCPBUGS-65684: Ignition fails with crypto/ecdh: invalid random source in FIPS 140-only mode
OCPBUGS-68354: Using multipath on the sysroot will fail to boot if less than 2 paths are present

This change was generated using:

plume cosa2stream \
    --target data/data/coreos/rhcos.json \
    --distro rhcos \
    --no-signatures \
    --name rhel-9.6 \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=9.6.20251212-1        \
    aarch64=9.6.20251212-1       \
    s390x=9.6.20251212-1         \
    ppc64le=9.6.20251212-1

Signed-off-by: Tiago Bueno <[email protected]>
@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. labels Dec 29, 2025
@openshift-ci-robot
Copy link
Contributor

@tlbueno: This pull request references Jira Issue OCPBUGS-66355, 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-66355 to depend on a bug targeting a version in 4.22.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:

OCPBUGS-66355: Update the RHCOS 4.21 bootimage metadata to 9.6.20251212-1
The changes done here will update the RHCOS 4.21 bootimage metadata and
address the following issues:

OCPBUGS-61669: [4.21] coreos-boot-disk link not working with multipath on early boot
OCPBUGS-65669: Cannot use auto-forward kargs (like ip=) with coreos-installer (iso|pxe) customize
OCPBUGS-65684: Ignition fails with crypto/ecdh: invalid random source in FIPS 140-only mode
OCPBUGS-68354: Using multipath on the sysroot will fail to boot if less than 2 paths are present

This change was generated using:

plume cosa2stream \
   --target data/data/coreos/rhcos.json \
   --distro rhcos \
   --no-signatures \
   --name rhel-9.6 \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=9.6.20251212-1        \
   aarch64=9.6.20251212-1       \
   s390x=9.6.20251212-1         \
   ppc64le=9.6.20251212-1

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 29, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 29, 2025

[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 jmarrero 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:

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

@tlbueno
Copy link
Member Author

tlbueno commented Dec 29, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@tlbueno: This pull request references Jira Issue OCPBUGS-66355, which is invalid:

  • expected Jira Issue OCPBUGS-66355 to depend on a bug targeting a version in 4.22.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.

@tlbueno
Copy link
Member Author

tlbueno commented Dec 29, 2025

openshift-ci-robot complains about a jira for 4.22 version. Atm RHCOS bot do not support 4.22 and for that reason the jira for 4.22 was not created. I will wait to get it fixed after the holidays then I can add a bump for 4.22 as well.

@tlbueno
Copy link
Member Author

tlbueno commented Dec 29, 2025

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 29, 2025
@tlbueno
Copy link
Member Author

tlbueno commented Dec 30, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 30, 2025

@tlbueno: The following test 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/okd-scos-images 92b90a1 link true /test okd-scos-images

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants