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

Bug 2095319: bump RHCOS 4.10 bootimage metadata #6095

Merged

Conversation

mike-nguyen
Copy link
Member

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

BZ 2059305 [tracker] HPE Synergy 480 Gen10 Plus servers fail to boot control plane nodes with kernel panic

Changes generated with:

plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --url https://rhcos-redirector.apps.art.xq1c.p1.openshiftapps.com/art/storage/releases --no-signatures x86_64=410.84.202207061638-0 aarch64=410.84.202207051516-0 s390x=410.84.202207060728-0 ppc64le=410.84.202207061403-0

@openshift-ci openshift-ci bot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium 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 Jul 7, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2022

@mike-nguyen: This pull request references Bugzilla bug 2095319, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.z) matches configured target release for branch (4.10.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2093126 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2093126 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

In response to this:

Bug 2095319: bump RHCOS 4.10 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
Copy link
Contributor

openshift-ci bot commented Jul 7, 2022

@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: mike-nguyen.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@mike-nguyen: This pull request references Bugzilla bug 2095319, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.z) matches configured target release for branch (4.10.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2093126 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2093126 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

In response to this:

Bug 2095319: bump RHCOS 4.10 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.

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 openshift-ci bot requested review from aaradhak and ashcrow July 7, 2022 14:25
@mike-nguyen
Copy link
Member Author

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2022

@mike-nguyen: This pull request references Bugzilla bug 2095319, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.z) matches configured target release for branch (4.10.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2093126 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2093126 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

Requesting review from QA contact:
/cc @aaradhak

In response to this:

/bugzilla 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.

@miabbott
Copy link
Member

miabbott commented Jul 7, 2022

/lgtm

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

aaradhak commented Jul 7, 2022

/lgtm

@mike-nguyen
Copy link
Member Author

/retest

@mike-nguyen
Copy link
Member Author

mike-nguyen commented Jul 11, 2022

@sadasu can we get a backport-risk-asssessed label on this? This is an RHCOS boot image bump like #5932

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

BZ 2059305 [tracker] HPE Synergy 480 Gen10 Plus servers fail to boot control plane nodes with kernel panic

Changes generated with:
```
plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --url https://rhcos.mirror.openshift.com/art/storage/releases --no-signatures x86_64=410.84.202207061638-0 aarch64=410.84.202207051516-0 s390x=410.84.202207060728-0 ppc64le=410.84.202207061403-0
```
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 11, 2022
@mike-nguyen
Copy link
Member Author

mike-nguyen commented Jul 11, 2022

Pushed a change to the redirector to match #6109. No changes to actual versions used. @miabbott can you give this another review?

@mike-nguyen
Copy link
Member Author

/retest

1 similar comment
@mike-nguyen
Copy link
Member Author

/retest

@miabbott
Copy link
Member

/lgtm

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

vfreex commented Jul 19, 2022

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 19, 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-azurestack da91dfe link false /test e2e-azurestack
ci/prow/e2e-aws-single-node da91dfe link false /test e2e-aws-single-node
ci/prow/e2e-ibmcloud da91dfe link false /test e2e-ibmcloud
ci/prow/e2e-azure-upi da91dfe link false /test e2e-azure-upi
ci/prow/e2e-crc da91dfe link false /test e2e-crc
ci/prow/e2e-azurestack-upi da91dfe link false /test e2e-azurestack-upi

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.

@mike-nguyen
Copy link
Member Author

all required tests have passed

Copy link
Contributor

@aaradhak aaradhak 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 Jul 19, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aaradhak

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 19, 2022
@mike-nguyen
Copy link
Member Author

@sadasu can you add a backport-risk-asssessed label on this?

@gpei can you add a cherry-picked-approved label?

This is an RHCOS boot image bump like #5932 and blocks the 4.9 and 4.8 boot image bumps.

@gpei
Copy link
Contributor

gpei commented Jul 20, 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 Jul 20, 2022
@patrickdillon
Copy link
Contributor

/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 21, 2022
@openshift-merge-robot openshift-merge-robot merged commit 6db5fb9 into openshift:release-4.10 Jul 21, 2022
30 of 36 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 21, 2022

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

Bugzilla bug 2095319 has been moved to the MODIFIED state.

In response to this:

Bug 2095319: bump RHCOS 4.10 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.

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. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants