Skip to content

Conversation

@tlbueno
Copy link
Member

@tlbueno tlbueno commented Nov 20, 2025

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

  • OCPBUGS-64613: [4.18] coreos-boot-disk link not working with multipath on early boot

This change was generated using:

plume cosa2stream \
    --target data/data/coreos/rhcos.json \
    --distro rhcos \
    --no-signatures \
    --name 4.18-9.4 \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=418.94.202511191518-0 \
    aarch64=418.94.202511191518-0 \
    s390x=418.94.202511191518-0 \
    ppc64le=418.94.202511191518-0

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

- OCPBUGS-64613: [4.18] coreos-boot-disk link not working with multipath on early boot

This change was generated using:

plume cosa2stream \
    --target data/data/coreos/rhcos.json \
    --distro rhcos \
    --no-signatures \
    --name 4.18-9.4 \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=418.94.202511191518-0 \
    aarch64=418.94.202511191518-0 \
    s390x=418.94.202511191518-0 \
    ppc64le=418.94.202511191518-0

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 Nov 20, 2025
@openshift-ci-robot
Copy link
Contributor

@tlbueno: This pull request references Jira Issue OCPBUGS-65588, 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 dependent Jira Issue OCPBUGS-65587 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Won't Do) instead

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.

In response to this:

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

  • OCPBUGS-64613: [4.18] coreos-boot-disk link not working with multipath on early boot

This change was generated using:

plume cosa2stream \
   --target data/data/coreos/rhcos.json \
   --distro rhcos \
   --no-signatures \
   --name 4.18-9.4 \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=418.94.202511191518-0 \
   aarch64=418.94.202511191518-0 \
   s390x=418.94.202511191518-0 \
   ppc64le=418.94.202511191518-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-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 Nov 20, 2025
@tlbueno
Copy link
Member Author

tlbueno commented Nov 20, 2025

/test e2e-openstack-ovn

1 similar comment
@tlbueno
Copy link
Member Author

tlbueno commented Nov 21, 2025

/test e2e-openstack-ovn

@jbtrystram
Copy link
Contributor

/test e2e-openstack-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jbtrystram

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 21, 2025
@sdodson
Copy link
Member

sdodson commented Nov 21, 2025

/label jira/valid-bug backport-risk-assessed
/unlabel jira/invalid-bug

@tlbueno
Copy link
Member Author

tlbueno commented Nov 21, 2025

/test e2e-openstack-ovn

@sdodson
Copy link
Member

sdodson commented Nov 21, 2025

/label jira/valid-bug backport-risk-assessed

@sdodson sdodson added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 21, 2025
@sdodson
Copy link
Member

sdodson commented Nov 21, 2025

/lgtm
/verified by CI
/override ci/prow/e2e-openstack-ovn
Has not built or passed on any other PR today

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-openstack-ovn

In response to this:

/lgtm
/verified by CI
/override ci/prow/e2e-openstack-ovn
Has not built or passed on any other PR today

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.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 21, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 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/e2e-openstack-ovn d4714b7 link true /test e2e-openstack-ovn

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.

@openshift-ci-robot
Copy link
Contributor

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

In response to this:

/lgtm
/verified by CI
/override ci/prow/e2e-openstack-ovn
Has not built or passed on any other PR today

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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 50225a8 into openshift:release-4.18 Nov 21, 2025
19 checks passed
@openshift-ci-robot
Copy link
Contributor

@tlbueno: Jira Issue Verification Checks: Jira Issue OCPBUGS-65588
✔️ 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-65588 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

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

  • OCPBUGS-64613: [4.18] coreos-boot-disk link not working with multipath on early boot

This change was generated using:

plume cosa2stream \
   --target data/data/coreos/rhcos.json \
   --distro rhcos \
   --no-signatures \
   --name 4.18-9.4 \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=418.94.202511191518-0 \
   aarch64=418.94.202511191518-0 \
   s390x=418.94.202511191518-0 \
   ppc64le=418.94.202511191518-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
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-11-22-072148

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.

5 participants