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-3362: bump RHCOS 4.11 bootimage metadata #6720

Merged
merged 1 commit into from Dec 23, 2022
Merged

OCPBUGS-3362: bump RHCOS 4.11 bootimage metadata #6720

merged 1 commit into from Dec 23, 2022

Conversation

mike-nguyen
Copy link
Member

These changes will update the RHCOS 4.11 boot image metadata in the installer which includes the fixes for the following:

OCPBUGS-2321 RHCOS VM fails to boot on IBM Power (ppc64le) - 4.11

These changes were generated with the following command

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

@mike-nguyen
bump RHCOS 4.11 bootimage metadata
8c1ebde 
These changes will update the RHCOS 4.11 boot image metadata in the
installer which includes the fixes for the following:

OCPBUGS-2321 RHCOS VM fails to boot on IBM Power (ppc64le) - 4.11

These changes were generated with the following command
```
plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --no-signatures --url https://rhcos.mirror.openshift.com/art/storage/prod/streams x86_64=411.86.202212072103-0 aarch64=411.86.202212072103-0 s390x=411.86.202212072103-0 ppc64le=411.86.202212072103-0
```
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 19, 2022

@mike-nguyen: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-3362: bump RHCOS 4.11 bootimage metadata

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.

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

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

  • expected dependent Jira Issue OCPBUGS-2997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is POST 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:

These changes will update the RHCOS 4.11 boot image metadata in the installer which includes the fixes for the following:

OCPBUGS-2321 RHCOS VM fails to boot on IBM Power (ppc64le) - 4.11

These changes were generated with the following command

plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --no-signatures --url https://rhcos.mirror.openshift.com/art/storage/prod/streams x86_64=411.86.202212072103-0 aarch64=411.86.202212072103-0 s390x=411.86.202212072103-0 ppc64le=411.86.202212072103-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 kubernetes/test-infra repository.

@mike-nguyen
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-2997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is MODIFIED 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.

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 kubernetes/test-infra 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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Dec 20, 2022
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-3362, 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.11.z) matches configured target version for branch (4.11.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-2997 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-2997 targets the "4.12.0" version, which is one of the valid target versions: 4.12.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 kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 20, 2022
@openshift-ci openshift-ci bot requested a review from aaradhak December 20, 2022 18:47
@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 Dec 20, 2022
@jlebon
Copy link
Member

jlebon commented Dec 20, 2022

/approve
/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 Dec 20, 2022
@mike-nguyen
Copy link
Member Author

@mgahagan73 can I get a /label cherry-pick-approved on this PR ? It is a bump to the RHCOS used during bootstrap but for 4.11.

@HuijingHei
Copy link
Contributor

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 21, 2022

@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/e2e-aws-upi-proxy 8c1ebde link false /test e2e-aws-upi-proxy
ci/prow/e2e-libvirt 8c1ebde link false /test e2e-libvirt
ci/prow/e2e-ibmcloud 8c1ebde link false /test e2e-ibmcloud
ci/prow/e2e-crc 8c1ebde link false /test e2e-crc

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.

@gpei
Copy link
Contributor

gpei commented Dec 23, 2022

/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 Dec 23, 2022
HuijingHei
HuijingHei approved these changes Dec 23, 2022
View reviewed changes
Copy link
Contributor

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

openshift-ci bot commented Dec 23, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HuijingHei, jlebon

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-robot openshift-merge-robot merged commit 616d135 into openshift:release-4.11 Dec 23, 2022
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: All pull requests linked via external trackers have merged:

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

In response to this:

These changes will update the RHCOS 4.11 boot image metadata in the installer which includes the fixes for the following:

OCPBUGS-2321 RHCOS VM fails to boot on IBM Power (ppc64le) - 4.11

These changes were generated with the following command

plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --no-signatures --url https://rhcos.mirror.openshift.com/art/storage/prod/streams x86_64=411.86.202212072103-0 aarch64=411.86.202212072103-0 s390x=411.86.202212072103-0 ppc64le=411.86.202212072103-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 kubernetes/test-infra repository.

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

@HuijingHei HuijingHei HuijingHei approved these changes

@gursewak1997 gursewak1997 Awaiting requested review from gursewak1997

@jmarrero jmarrero Awaiting requested review from jmarrero

@aaradhak aaradhak Awaiting requested review from aaradhak

Assignees

@jlebon jlebon

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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. 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
6 participants
@mike-nguyen @openshift-ci-robot @jlebon @HuijingHei @gpei @openshift-merge-robot