ci-operator/templates/openshift/installer/cluster-launch-installer-*: Drop eastus Azure region #5182
Conversation
openshift-ci-robot
added
size/XS
… Drop eastus Azure region Azure seems to have a shortage of VMs there today, with failures like [1]: level=error msg="Error: Code=\"ZonalAllocationFailed\" Message=\"Allocation failed. We do not have sufficient capacity for the requested VM size in this zone. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance\"" You can see that failure was for eastus with: $ curl -s https://storage.googleapis.com/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-azure-serial-4.2/244/artifacts/e2e-azure-serial/installer/terraform.tfstate | jq -r '.resources[] | select(.name == "ignition_bootstrap").instances[].attributes.content | fromjson | .storage.files[] | select(.path == "/opt/openshift/manifests/cluster-config.yaml").contents.source' | sed 's/.*,//' | base64 -d | grep region region: eastus Jerry also found an eastus2 failure like this. While we could drop to an even weighting among the three remaining zones, in this commit I'm triple-weighting centralus because we have extra capacity there. Before 4d08a9d (ci-operator/templates/openshift/installer/cluster-launch-installer-*: Random Azure regions, 2019-09-18, openshift#5081) we were serving all 20 of our Azure leases out of centralus. [1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-azure-serial-4.2/244
wking
force-pushed
the
drop-azure-eastus
branch
from
b8f353f to
00fa1c5
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking, yuqi-zhang 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 |
|
@wking: Updated the following 4 configmaps:
In response to this:
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. |
|
@wking: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
…aller-*: Drop eastus Azure region" This reverts commit 00fa1c5, openshift#5182. Now we're having a problem with centralus: $ curl -s 'https://search.svc.ci.openshift.org/search?name=azure&maxAge=24h&context=5&search=We+do+not+have+sufficient+capacity+for+the+requested+VM+size+in+this+zone' | jq -r '. | to_entries[].value | to_entries[].value[].context[]' | sed -n 's/Azure region: //p' | sort | uniq -c | sort -n 18 centralus So de-emphasize it by reverting the earlier commit.
Azure seems to have a shortage of VMs there today, with failures like:
You can see that failure was for eastus with:
While we could drop to an even weighting among the three remaining zones, in this commit I'm double-waiting centralus because we have extra capacity there. Before 4d08a9d (#5081) we were serving all 20 of our Azure leases out of centralus.