Bump AWS FIPS IPI jobs to m6a.2xlarge instances#82033
Conversation
The e2e-aws-ovn-fips jobs are hitting resource pressure on the default m6a.xlarge nodes. Set COMPUTE_NODE_TYPE and CONTROL_PLANE_INSTANCE_TYPE to m6a.2xlarge for the FIPS tests in current development releases (main/master, release-4.22, release-4.23) of installer, kubernetes, machine-config-operator and origin, plus the nightly-4.22/4.23 release periodics (including e2e-aws-ovn-fips-serial). Assisted-By: Claude Fable 5 Signed-off-by: Mat Kowalski <mko@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mkowalski The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (3)
WalkthroughThe CI configurations for OpenShift FIPS AWS e2e jobs now set both compute and control-plane instance types to ChangesFIPS AWS instance sizing
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-upgrade-fips-rhcos9-techpreview and periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-upgrade-fips are the two jobs on my radar, but I don't see them in the list of affected jobs. They must be using a slightly different step? The list of jobs above looks good, just needs more I think. Possibility the list is not exhaustive, which could be verified by using /pj-rehearse on the job names I just gave, but it looks to me like upgrade was missed. Once that's identified then you can rehearse on a selection of the jobs above, and we can verify they got the right instances sizes and hopefully saw no cpu disruption. |
Follow-up to the previous commit: the e2e-aws-ovn-upgrade-fips family and the nightly-5.0 FIPS jobs were missed. Add the same COMPUTE_NODE_TYPE/CONTROL_PLANE_INSTANCE_TYPE=m6a.2xlarge overrides to all e2e-aws-ovn*fips* tests in nightly-4.22, nightly-4.23 and nightly-5.0 release configs. Assisted-By: Claude Fable 5 Signed-off-by: Mat Kowalski <mko@redhat.com>
|
Good catch — the
|
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-upgrade-fips periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-upgrade-fips-rhcos9-techpreview periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-fips |
|
@mkowalski: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
A total of 26 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
On hold while we see if openshift/origin#31377 works |
|
/hold |
openshift-ci
Bot
added
the
do-not-merge/hold
|
@mkowalski: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
2 participants
Sets
COMPUTE_NODE_TYPEandCONTROL_PLANE_INSTANCE_TYPEtom6a.2xlargefore2e-aws-ovn-fips(ande2e-aws-ovn-fips-serial) tests in current development releases (main/master, release-4.22, release-4.23) of installer, kubernetes, machine-config-operator, origin, and the nightly-4.22/4.23 release periodics, per Slack thread.Replaces #82030, which wrongly targeted CVP cluster pools instead of the IPI jobs.
Summary by CodeRabbit
Updates OpenShift CI “AWS OVN FIPS” IPI e2e jobs to run on
m6a.2xlargeinstead of the default instance sizing by settingCOMPUTE_NODE_TYPEandCONTROL_PLANE_INSTANCE_TYPEtom6a.2xlarge. This is applied across the OpenShift component CI config for installer, Kubernetes, machine-config-operator, and origin (development/current release configs), and across nightly release periodics for 4.22 and 4.23 (including the serial and upgrade/no-NAT variants). A follow-up extends the same instance overrides to the previously-missed upgrade FIPS family and the nightly-5.0 FIPS jobs (including the RHCOs9 techpreview variants), ensuring alle2e-aws-ovn*fips*nightly configurations consistently usem6a.2xlarge.