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

Jump to bottom

Bug 2045771: bump RHCOS 4.10 bootimage metadata #5932

Merged
merged 1 commit into from May 24, 2022
Merged

Bug 2045771: bump RHCOS 4.10 bootimage metadata #5932

merged 1 commit into from May 24, 2022

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:

Bug 2077998: Publish RHEL CoreOS AMIs in AWS ap-southeast-3 region

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.202205191234-0 aarch64=410.84.202205191023-0 s390x=410.84.202205191234-0 ppc64le=410.84.202205191722-0

@mike-nguyen
Bug 2045771: bump RHCOS 4.10 bootimage metadata
94ab59f 
These changes will update the RHCOS 4.10 boot image metadata in the
installer which includes the fixes for the following BZs:

Bug 2077998: Publish RHEL CoreOS AMIs in AWS ap-southeast-3 region

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.202205191234-0 aarch64=410.84.202205191023-0 s390x=410.84.202205191234-0 ppc64le=410.84.202205191722-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 May 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 19, 2022

@mike-nguyen: This pull request references Bugzilla bug 2045771, 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.

8 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 2047935 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent bug Bugzilla bug 2065893 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2047935 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • dependent Bugzilla bug 2065893 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 2045771: 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 May 19, 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 2045771, 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.

8 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 2047935 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent bug Bugzilla bug 2065893 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2047935 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • dependent Bugzilla bug 2065893 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 2045771: 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.

@mike-nguyen
Copy link
Member Author

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 19, 2022

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

8 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 2047935 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent bug Bugzilla bug 2065893 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2047935 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • dependent Bugzilla bug 2065893 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.

@openshift-ci openshift-ci bot requested a review from aaradhak May 19, 2022 20:52
@mike-nguyen
Copy link
Member Author

/retest

3 similar comments
@mike-nguyen
Copy link
Member Author

/retest

@mike-nguyen
Copy link
Member Author

/retest

@HuijingHei
Copy link
Contributor

/retest

@mike-nguyen
Copy link
Member Author

The remaining failing tests have been failing for as far back as I can go in the prow job history.

miabbott
miabbott reviewed May 23, 2022
View reviewed changes
data/data/coreos/rhcos.json
Comment on lines -222 to -229
"powervs": {
"release": "410.84.202201251004-0",
"formats": {
"ova.gz": {
"disk": {
"location": "https://rhcos-redirector.apps.art.xq1c.p1.openshiftapps.com/art/storage/releases/rhcos-4.10-ppc64le/410.84.202201251004-0/ppc64le/rhcos-410.84.202201251004-0-powervs.ppc64le.ova.gz",
"sha256": "6ef2a5ba8a82a669e590ef38918f73b0924a9dd01d88fae1d18c71e611c52ee2",
"uncompressed-sha256": "114b265a4d9e9f3f8db8a79f6cd07955f09d918ee7d17b0ad7ecb04d16e31a70"
Copy link
Member

Choose a reason for hiding this comment

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

What happened to all the PowerVS artifacts and cloud uploads below?

Copy link
Member Author

Choose a reason for hiding this comment

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

powervs isn't supported in 4.10

Copy link
Contributor

Choose a reason for hiding this comment

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

yes. not needed for 4.10. the pipeline has also stopped generating Power VS artifacts.

Copy link
Member

Choose a reason for hiding this comment

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

thanks!

@miabbott
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 23, 2022
@travier
Copy link
Member

travier commented May 23, 2022

/retest

@travier
Copy link
Member

travier commented May 23, 2022

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 23, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: travier

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 May 23, 2022
@miabbott
Copy link
Member

/label backport-risk-assessed

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 23, 2022

@miabbott: Can not set label backport-risk-assessed: Must be member in one of these teams: []

In response to this:

/label backport-risk-assessed

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 May 23, 2022 •
edited

@miabbott: Can not set label backport-risk-assessed: Must be member in one of these teams: []

Well great, that is not helpful. AFAICT I'm configured to provide that label

https://github.com/openshift/release/blob/master/core-services/prow/02_config/openshift/os/_pluginconfig.yaml

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@Prashanth684
Copy link
Contributor

/label backport-risk-assessed
/label cherry-pick-approved

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@gpei
Copy link
Contributor

gpei commented May 24, 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 May 24, 2022
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

14 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@mike-nguyen
Copy link
Member Author

Is this change required just for 4.10? Was this merged into 4.11 via an earlier PR?

Each minor version of OCP requires a different version of RHCOS. The RHCOS bugs that require a new boot image fix issues related to initial provisioning. All other RHCOS bugs can be fixed through the RHCOS machine-os-content payload.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@sadasu
Copy link
Contributor

sadasu commented May 24, 2022

/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 May 24, 2022
@openshift-merge-robot openshift-merge-robot merged commit a4b45c9 into openshift:release-4.10 May 24, 2022
29 of 36 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 24, 2022

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

Bugzilla bug 2045771 has been moved to the MODIFIED state.

In response to this:

Bug 2045771: 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.

@miabbott miabbott mentioned this pull request Jun 3, 2022
Merged
This was referenced Jun 16, 2022
Merged
Merged
@mike-nguyen mike-nguyen mentioned this pull request Jul 11, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Prashanth684 Prashanth684 Prashanth684 left review comments

@miabbott miabbott miabbott left review comments

@travier travier travier approved these changes

@cgwalters cgwalters Awaiting requested review from cgwalters

@dustymabe dustymabe Awaiting requested review from dustymabe

@aaradhak aaradhak Awaiting requested review from aaradhak

Assignees

@miabbott miabbott

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

Successfully merging this pull request may close these issues.

None yet
9 participants
@mike-nguyen @HuijingHei @miabbott @travier @openshift-bot @Prashanth684 @sadasu @gpei @openshift-merge-robot