azure: switch sustaining autorelease-412 jobs to azure-autorelease-qe profile#80553
Conversation
|
Warning Review limit reached
More reviews will be available in 16 minutes and 3 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (6)
📒 Files selected for processing (17)
WalkthroughAcross 38 CI operator YAML configuration files spanning OpenShift releases 4.12 through 5.0, Azure IPI FIPS and UPI test jobs are systematically migrated to use a unified ChangesAzure Cluster Profile Consolidation Across OCP 4.12–5.0
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Suggested reviewers
Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: redhat-chai-bot 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 |
|
/hold |
openshift-ci
Bot
added
the
do-not-merge/hold
redhat-chai-bot
force-pushed
the
autorelease-412-use-shared-azure-profile
branch
from
53710d3 to
a0e8dc8
Compare
|
[REHEARSALNOTIFIER]
A total of 74 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: |
…profile Moves all 4.12-4.17 autorelease jobs from the dedicated azure-sustaining-autorelease-412 cluster profile (60 eastus-only leases) to the shared openshift-org-azure profile (multi-region, multi-subscription). This resolves SkuNotAvailable failures for Standard_D8as_v5 in eastus. Also updates BASE_DOMAIN from sustaining-az-412.azure.devcluster.openshift.com to ci.azure.devcluster.openshift.com.
redhat-chai-bot
force-pushed
the
autorelease-412-use-shared-azure-profile
branch
from
a0e8dc8 to
b08ec93
Compare
|
@redhat-chai-bot: |
|
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-automated-release-stable-4.14-upgrade-from-stable-4.14-azure-ipi-fips-f999 |
|
@jupierce: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@redhat-chai-bot: all tests passed! 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
Background
The
azure-sustaining-autorelease-412cluster profile has a standalone boskos quota-slice with all 60 leases concentrated ineastusonly. Since commit 14641eb switched Azure CI defaults toStandard_D8as_v5, and this instance type has capacity constraints ineastus, all autorelease jobs using this profile have been failing withSkuNotAvailableerrors (12+ consecutive failures since June 11).Changes
Switches all 4.12–4.17 autorelease CI job configs from the dedicated
azure-sustaining-autorelease-412profile toazure-autorelease-qe, which:eastus2(noteastus), avoiding the capacity issueopenshift/openshift-tests-privateincluster-profiles-config.yamlSpecific changes per file (17 ci-operator config files):
cluster_profile: azure-sustaining-autorelease-412→cluster_profile: azure-autorelease-qeBASE_DOMAIN: sustaining-az-412.azure.devcluster.openshift.com→BASE_DOMAIN: qe.azure.devcluster.openshift.com6 generated prowjob files under
ci-operator/jobs/are regenerated bymake jobs.Affected releases
4.12, 4.13, 4.14, 4.15, 4.16, 4.17 — all autorelease and upgrade-from-stable jobs that were using the sustaining-412 profile.
Note
The
azure-autorelease-qeprofile has 7 boskos slices in eastus2, which is significantly less capacity than the previous 60-slice eastus pool. If this becomes a bottleneck for autorelease job throughput, theazure-autorelease-qe-quota-slicepool may need to be expanded.References
Summary by CodeRabbit
This PR updates CI configuration for automated release jobs (versions 4.12–4.17) in the
openshift/openshift-tests-privaterepository to resolve Azure capacity constraints. Specifically, 17 configuration files are updated to migrate from theazure-sustaining-autorelease-412cluster profile to the sharedazure-autorelease-qeprofile.Practical Impact:
azure-ipi-fips-f999andazure-upi-f999across multiple release branches) will now run on theazure-autorelease-qecluster profile instead of the dedicated sustaining profileeastus(experiencingSkuNotAvailableerrors for theStandard_D8as_v5instance type) toeastus2sustaining-az-412.azure.devcluster.openshift.comtoqe.azure.devcluster.openshift.comChanges across all 17 files:
cluster_profile:azure-sustaining-autorelease-412→azure-autorelease-qeBASE_DOMAIN:sustaining-az-412.azure.devcluster.openshift.com→qe.azure.devcluster.openshift.comThis aligns the 4.12–4.17 autorelease configurations with the approach already in use for 4.18+ releases, removing a capacity bottleneck that had caused 12+ consecutive job failures.