Skip to content

Conversation

@HuijingHei
Copy link
Contributor

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

  • OCPBUGS-65974: Cannot use auto-forward kargs (like ip=) with coreos-installer (iso|pxe) customize

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.202602022246-0 \
    aarch64=418.94.202602022246-0 \
    s390x=418.94.202602022246-0 \
    ppc64le=418.94.202602022246-0

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

- OCPBUGS-65974: Cannot use auto-forward kargs (like ip=) with
coreos-installer (iso|pxe) customize

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.202602022246-0 \
    aarch64=418.94.202602022246-0 \
    s390x=418.94.202602022246-0 \
    ppc64le=418.94.202602022246-0
```
@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 Feb 9, 2026
@openshift-ci-robot
Copy link
Contributor

@HuijingHei: This pull request references Jira Issue OCPBUGS-67203, 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.

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:

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

  • OCPBUGS-65974: Cannot use auto-forward kargs (like ip=) with coreos-installer (iso|pxe) customize

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.202602022246-0 \
   aarch64=418.94.202602022246-0 \
   s390x=418.94.202602022246-0 \
   ppc64le=418.94.202602022246-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
Copy link
Member

tlbueno commented Feb 9, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added 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 Feb 9, 2026
@openshift-ci-robot
Copy link
Contributor

@tlbueno: This pull request references Jira Issue OCPBUGS-67203, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-66358 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-66358 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (tbueno@redhat.com), skipping review request.

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.

Copy link
Member

@tlbueno tlbueno left a comment

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 added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2026
@HuijingHei
Copy link
Contributor Author

/test e2e-openstack-ovn

1 similar comment
@HuijingHei
Copy link
Contributor Author

/test e2e-openstack-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

@HuijingHei: all tests passed!

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.

@tlbueno
Copy link
Member

tlbueno commented Feb 11, 2026

@sdodson could you approve this one?

@sadasu
Copy link
Contributor

sadasu commented Feb 11, 2026

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 11, 2026
@sadasu
Copy link
Contributor

sadasu commented Feb 11, 2026

/verified by pre-submit jobs

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 11, 2026
@openshift-ci-robot
Copy link
Contributor

@sadasu: This PR has been marked as verified by pre-submit jobs.

Details

In response to this:

/verified by pre-submit jobs

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
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sadasu, 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 11, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 628239f into openshift:release-4.18 Feb 11, 2026
19 checks passed
@openshift-ci-robot
Copy link
Contributor

@HuijingHei: Jira Issue Verification Checks: Jira Issue OCPBUGS-67203
✔️ 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-67203 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:

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

  • OCPBUGS-65974: Cannot use auto-forward kargs (like ip=) with coreos-installer (iso|pxe) customize

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.202602022246-0 \
   aarch64=418.94.202602022246-0 \
   s390x=418.94.202602022246-0 \
   ppc64le=418.94.202602022246-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.

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.

4 participants