Skip to content

Conversation

@CourtCourt521
Copy link
Contributor

- What I did

I enabled the ManagedBootImage feature for the AWS platform as part of managing boot images via the MCO

- How to verify it

See the instructions in this PR for testing GCP for setting up the cluster.

#4083

Please note that with AWS instead of directly using one boot image for each cluster version like GCP does. AWS uses a specific boot image per region for each version and they are stored in the ami field

You can see each region and the value assigned to that ami in the coreos-bootimages configmap in the machine-config-operator namespace for validation that it's correct.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 25, 2024

@CourtCourt521: This pull request references MCO-1214 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.

Details

In response to this:

- What I did

I enabled the ManagedBootImage feature for the AWS platform as part of managing boot images via the MCO

- How to verify it

See the instructions in this PR for testing GCP for setting up the cluster.

#4083

Please note that with AWS instead of directly using one boot image for each cluster version like GCP does. AWS uses a specific boot image per region for each version and they are stored in the ami field

You can see each region and the value assigned to that ami in the coreos-bootimages configmap in the machine-config-operator namespace for validation that it's correct.

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 25, 2024
Copy link
Contributor

@yuqi-zhang yuqi-zhang left a comment

Choose a reason for hiding this comment

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

generally looks good! some comments inline

@sergiordlr
Copy link
Contributor

sergiordlr commented Aug 7, 2024

Verified using automated test cases for GCP (adapted to use AWS).

Automation has been adapted to support AWS (WIP still) https://github.com/openshift/openshift-tests-private/pull/18630

All test cases passed in AWS:

"[sig-mco] MCO Bootimages Author:sregidor-NonHyperShiftHOST-NonPreRelease-Medium-74238-BootImages not updated by default [Disruptive] [Serial]"
"[sig-mco] MCO Bootimages Author:sregidor-NonHyperShiftHOST-NonPreRelease-Medium-74239-ManagedBootImages. Restore Partial MachineSet images [Disruptive] [Serial]"
"[sig-mco] MCO Bootimages Author:sregidor-NonHyperShiftHOST-NonPreRelease-Medium-74240-ManagedBootImages. Restore All MachineSet images [Disruptive] [Serial]"
"[sig-mco] MCO Bootimages Author:sregidor-NonHyperShiftHOST-NonPreRelease-Medium-74751-ManagedBootImages. Fix errors [Disruptive] [Serial]"
"[sig-mco] MCO Bootimages Author:sregidor-NonHyperShiftHOST-NonPreRelease-Medium-74764-ManagedBootImages. Delete machineset when error [Disruptive] [Serial]"

In a GCP cluster those test cases passed too.

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Aug 7, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 7, 2024

@CourtCourt521: This pull request references MCO-1214 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.

Details

In response to this:

- What I did

I enabled the ManagedBootImage feature for the AWS platform as part of managing boot images via the MCO

- How to verify it

See the instructions in this PR for testing GCP for setting up the cluster.

#4083

Please note that with AWS instead of directly using one boot image for each cluster version like GCP does. AWS uses a specific boot image per region for each version and they are stored in the ami field

You can see each region and the value assigned to that ami in the coreos-bootimages configmap in the machine-config-operator namespace for validation that it's correct.

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.

@CourtCourt521
Copy link
Contributor Author

@yuqi-zhang

Points addressed and ready for another review!

@CourtCourt521 CourtCourt521 force-pushed the MCO-boot-Images branch 2 times, most recently from 0919dad to bb41500 Compare August 7, 2024 17:43
@djoshy
Copy link
Contributor

djoshy commented Aug 8, 2024

/test all

@djoshy
Copy link
Contributor

djoshy commented Aug 8, 2024

/retitle MCO-1214: Enabled boot images updates for AWS

@openshift-ci openshift-ci bot changed the title MCO-1214: Enabled AWS platform MCO-1214: Enabled boot images updates for AWS Aug 8, 2024
Copy link
Contributor

@yuqi-zhang yuqi-zhang left a comment

Choose a reason for hiding this comment

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

/lgtm

changes looks good to me, thanks!

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

openshift-ci bot commented Aug 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CourtCourt521, yuqi-zhang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Aug 8, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 217f607 and 2 for PR HEAD 3bb751a in total

@djoshy
Copy link
Contributor

djoshy commented Aug 8, 2024

/retest-required

1 similar comment
@djoshy
Copy link
Contributor

djoshy commented Aug 8, 2024

/retest-required

@djoshy
Copy link
Contributor

djoshy commented Aug 8, 2024

/override ci/prow/e2e-hypershift

Overriding as it has passed this test before and it is behind feature gate.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 8, 2024

@djoshy: Overrode contexts on behalf of djoshy: ci/prow/e2e-hypershift

Details

In response to this:

/override ci/prow/e2e-hypershift

Overriding as it has passed this test before and it is behind feature gate.

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 9c7a000 into openshift:master Aug 8, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 8, 2024

@CourtCourt521: The following test 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-vsphere-ovn-upi 3bb751a link false /test e2e-vsphere-ovn-upi

Full PR test history. Your PR dashboard.

Details

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.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-config-operator
This PR has been included in build ose-machine-config-operator-container-v4.18.0-202408081846.p0.g9c7a000.assembly.stream.el9.
All builds following this will include this PR.

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. 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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants