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.

Sign up for GitHub

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

Jump to bottom

OCPBUGS-30601: update RHCOS 4.15 bootimage metadata to 415.92.202402201450-0 #8122

Merged
merged 1 commit into from Mar 14, 2024
Merged

OCPBUGS-30601: update RHCOS 4.15 bootimage metadata to 415.92.202402201450-0 #8122

merged 1 commit into from Mar 14, 2024

Conversation

mike-nguyen
Copy link
Member

These changes will update the RHCOS 4.15 boot image metadata.

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.202402201450-0                                      \
    aarch64=415.92.202402201450-0                                     \
    s390x=415.92.202402201450-0                                       \
    ppc64le=415.92.202402201450-0

@mike-nguyen
update RHCOS 4.15 bootimage metadata to 415.92.202402201450-0
255b209 
These changes will update the RHCOS 4.15 boot image metadata.

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.202402201450-0                                      \
    aarch64=415.92.202402201450-0                                     \
    s390x=415.92.202402201450-0                                       \
    ppc64le=415.92.202402201450-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 Mar 7, 2024
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-30601, which is invalid:

  • expected Jira Issue OCPBUGS-30601 to depend on a bug targeting a version in 4.16.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

In response to this:

These changes will update the RHCOS 4.15 boot image metadata.

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.202402201450-0                                      \
   aarch64=415.92.202402201450-0                                     \
   s390x=415.92.202402201450-0                                       \
   ppc64le=415.92.202402201450-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

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

@gpei can we get a cherry-pick-approved label on this bootimage bump?

@gpei
Copy link
Contributor

gpei commented Mar 8, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 8, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 8, 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 255b209 link false /test okd-scos-e2e-vsphere
ci/prow/okd-scos-e2e-aws-upgrade 255b209 link false /test okd-scos-e2e-aws-upgrade
ci/prow/okd-scos-e2e-gcp 255b209 link false /test okd-scos-e2e-gcp
ci/prow/okd-scos-e2e-aws-ovn 255b209 link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-scos-e2e-gcp-ovn-upgrade 255b209 link false /test okd-scos-e2e-gcp-ovn-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/test-infra repository. I understand the commands that are listed here.

c4rt0
c4rt0 approved these changes Mar 8, 2024
View reviewed changes
Copy link
Contributor

@c4rt0 c4rt0 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 lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 8, 2024
yasminvalim
yasminvalim approved these changes Mar 8, 2024
View reviewed changes
Copy link
Contributor

@yasminvalim yasminvalim left a comment

Choose a reason for hiding this comment

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

/LGTM

@HuijingHei
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@HuijingHei: This pull request references Jira Issue OCPBUGS-30601, which is invalid:

  • expected Jira Issue OCPBUGS-30601 to depend on a bug targeting a version in 4.16.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

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.

@HuijingHei
Copy link
Contributor

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

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

6 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)
  • dependent bug Jira Issue OCPBUGS-30600 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-30600 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • 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.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 14, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: c4rt0, HuijingHei, yasminvalim

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-merge-bot openshift-merge-bot bot merged commit 3743665 into openshift:release-4.15 Mar 14, 2024
27 of 32 checks passed
@openshift-ci-robot
Copy link
Contributor

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

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

In response to this:

These changes will update the RHCOS 4.15 boot image metadata.

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.202402201450-0                                      \
   aarch64=415.92.202402201450-0                                     \
   s390x=415.92.202402201450-0                                       \
   ppc64le=415.92.202402201450-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.15.0-0.nightly-2024-03-20-032212

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

@c4rt0 c4rt0 c4rt0 approved these changes

@HuijingHei HuijingHei HuijingHei approved these changes

@yasminvalim yasminvalim yasminvalim approved these changes

@aaradhak aaradhak Awaiting requested review from aaradhak

@jbtrystram jbtrystram Awaiting requested review from jbtrystram

Assignees

@c4rt0 c4rt0

@yasminvalim yasminvalim

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
7 participants
@mike-nguyen @openshift-ci-robot @gpei @HuijingHei @openshift-merge-robot @c4rt0 @yasminvalim