Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-37067: update RHCOS 4.15 bootimage metadata to 415.92.202407091355-0 #8746

Merged
merged 1 commit into from
Jul 18, 2024

Conversation

mike-nguyen
Copy link
Member

These changes will update the RHCOS 4.15 boot image metadata. Notable fixes are:

OCPBUGS-36815 - ISO image boot of OpenShift 4.14 causes kernel panic during SNO cluster installation on the QuantaEdge EGX77B-1U server

This change was generated using:

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

These changes will update the RHCOS 4.15 boot image metadata. Notable
fixes are:

OCPBUGS-36815 - ISO image boot of OpenShift 4.14 causes kernel panic during SNO cluster installation on the QuantaEdge EGX77B-1U server

This change was generated using:

```
plume cosa2stream --target data/data/coreos/rhcos.json                \
    --distro rhcos --no-signatures --name 4.15-9.2                    \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=415.92.202407091355-0                                      \
    aarch64=415.92.202407091355-0                                     \
    s390x=415.92.202407091355-0                                       \
    ppc64le=415.92.202407091355-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 Jul 17, 2024
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-37067, 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"

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:

These changes will update the RHCOS 4.15 boot image metadata. Notable fixes are:

OCPBUGS-36815 - ISO image boot of OpenShift 4.14 causes kernel panic during SNO cluster installation on the QuantaEdge EGX77B-1U server

This change was generated using:

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

@mike-nguyen
Copy link
Member Author

/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 Jul 17, 2024
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-37067, 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.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-36324 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-36324 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
  • bug has dependents

Requesting review from QA contact:
/cc @aaradhak

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.

@mike-nguyen
Copy link
Member Author

/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 Jul 17, 2024
@mike-nguyen
Copy link
Member Author

@gpei can I get a cherry-pick-approved on this RHCOS bootimage bump?

Copy link
Contributor

openshift-ci bot commented Jul 17, 2024

@mike-nguyen: 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/okd-scos-e2e-vsphere 3297465 link false /test okd-scos-e2e-vsphere
ci/prow/e2e-aws-ovn-upgrade 3297465 link false /test e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn 3297465 link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-scos-e2e-gcp 3297465 link false /test okd-scos-e2e-gcp
ci/prow/okd-e2e-aws-ovn-upgrade 3297465 link false /test okd-e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-workers-rhel8 3297465 link false /test e2e-aws-ovn-workers-rhel8
ci/prow/okd-scos-e2e-gcp-ovn-upgrade 3297465 link false /test okd-scos-e2e-gcp-ovn-upgrade
ci/prow/okd-scos-e2e-aws-upgrade 3297465 link false /test okd-scos-e2e-aws-upgrade

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.

@sdodson sdodson added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jul 18, 2024
@sdodson
Copy link
Member

sdodson commented Jul 18, 2024

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 18, 2024
Copy link
Contributor

openshift-ci bot commented Jul 18, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sdodson

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 Jul 18, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit c48f860 into openshift:release-4.15 Jul 18, 2024
24 of 32 checks passed
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: Jira Issue OCPBUGS-37067: All pull requests linked via external trackers have merged:

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

In response to this:

These changes will update the RHCOS 4.15 boot image metadata. Notable fixes are:

OCPBUGS-36815 - ISO image boot of OpenShift 4.14 causes kernel panic during SNO cluster installation on the QuantaEdge EGX77B-1U server

This change was generated using:

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

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-installer-altinfra-container-v4.15.0-202407180207.p0.gc48f860.assembly.stream.el8 for distgit ose-installer-altinfra.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.15.0-0.nightly-2024-07-20-065442

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants