Skip to content

ci-operator/step-registry/ipi/conf/gcp: Get region from Boskos lease #14324

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

Merged

Conversation

wking
Copy link
Member

@wking wking commented Dec 14, 2020

Like 7aa198b (#12584), but for AWS. This sets us up for sharding GCP by region, if we ever need that (e.g. GCP has an outage in one region).

I'm leaving ci-operator/templates alone; hopefully those will be gone soon. I've already updated ci-tools with openshift/ci-tools@00ebab17e1 (openshift/ci-tools#1527).

I still wish the end-to-end suite pulled the region out of the cluster itself, but until it does, lean on the Infrastructure status like we've been doing for AWS since bf0a271 (#2507).

Like 7aa198b (ci-operator/step-registry/ipi/conf/azure: Get region
from Boskos lease, 2020-10-14, openshift#12584), but for AWS.  This sets us up
for sharding GCP by region, if we ever need that (e.g. GCP has an
outage in one region).

I'm leaving ci-operator/templates alone; hopefully those will be gone
soon.  I've already updated ci-tools with
openshift/ci-tools@00ebab17e1 (pkg/steps/clusterinstall/template: Get
region from Boskos lease, 2020-12-11, openshift/ci-tools#1527).

I still wish the end-to-end suite pulled the region out of the cluster
itself, but until it does, lean on the Infrastructure status [1] like
we've been doing for AWS since bf0a271 (AWS e2e provider should
identify zone and master and multizone, 2019-01-05, openshift#2507).

[1]: https://github.com/openshift/api/blob/164a2fb63b5f12918c439a5a0a768aa911bcad99/config/v1/types_infrastructure.go#L327-L328
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 14, 2020
@openshift-merge-robot
Copy link
Contributor

@wking: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift/cluster-samples-operator/master/e2e-aws-jenkins e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-upi-xpn e9df372 link /test pj-rehearse
ci/rehearse/open-cluster-management/registration-operator/master/e2e e9df372 link /test pj-rehearse
ci/rehearse/openshift/cincinnati-operator/release-4.5/operator-e2e e9df372 link /test pj-rehearse
ci/rehearse/openshift/aws-ebs-csi-driver/master/e2e-aws-csi e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/release-4.6/e2e-agnostic e9df372 link /test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-aws-proxy e9df372 link /test pj-rehearse
ci/rehearse/openshift/oc/release-4.2/e2e-cmd e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-shared-vpc e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-ovn-step-registry e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-azure/master/e2e-upgrade e9df372 link /test pj-rehearse
ci/rehearse/openshift/cincinnati/master/e2e e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-vsphere-ovn e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-azure-shared-vpc e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-workers-rhel7 e9df372 link /test pj-rehearse
ci/rehearse/cri-o/cri-o/master/e2e-agnostic e9df372 link /test pj-rehearse
ci/rehearse/openshift/machine-api-operator/master/e2e-vsphere-operator e9df372 link /test pj-rehearse
ci/rehearse/kubevirt/hyperconverged-cluster-operator/master/hco-e2e-image-index-gcp e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-ovn-hybrid-step-registry e9df372 link /test pj-rehearse
ci/prow/pj-rehearse e9df372 link /test pj-rehearse

Full PR test history. Your PR dashboard.

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.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2021
@ironcladlou
Copy link
Contributor

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2021

@wking: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift/cluster-api-provider-kubevirt/master/e2e-kubevirt e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-openstack/master/e2e-upgrade e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-image-registry-operator/release-4.5/e2e-vsphere e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-openstack-ipi e9df372 link /test pj-rehearse
ci/rehearse/openshift/aws-ebs-csi-driver/release-4.5/e2e-aws-csi e9df372 link /test pj-rehearse
ci/rehearse/openshift/aws-ebs-csi-driver-operator/release-4.5/e2e-operator e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-azure-shared-vpc e9df372 link /test pj-rehearse
ci/rehearse/devfile/integration-tests/master/v4.7.console-e2e-gcp-console e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-csi-snapshot-controller-operator/master/e2e-gcp-csi e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/master/e2e-operator e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-kube-apiserver-operator/master/k8s-e2e-gcp e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/master/e2e-gcp-five-control-plane-replicas e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-samples-operator/master/e2e-aws-jenkins e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-workers-rhel7 e9df372 link /test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-aws-proxy e9df372 link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/master/e2e-upgrade e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-upi e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-azure/master/e2e-upgrade e9df372 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-upi-xpn e9df372 link /test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/master/e2e-agnostic e9df372 link /test pj-rehearse
ci/rehearse/openshift/kubernetes/master/e2e-agnostic-cmd e9df372 link /test pj-rehearse
ci/prow/pj-rehearse e9df372 link /test pj-rehearse

Full PR test history. Your PR dashboard.

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.

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2021
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: droslean, wking

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-merge-robot openshift-merge-robot merged commit dc96937 into openshift:master Apr 15, 2021
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the step-registry configmap in namespace ci at cluster app.ci using the following files:

  • key ipi-conf-gcp-commands.sh using file ci-operator/step-registry/ipi/conf/gcp/ipi-conf-gcp-commands.sh
  • key openshift-e2e-test-commands.sh using file ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-commands.sh

In response to this:

Like 7aa198b (#12584), but for AWS. This sets us up for sharding GCP by region, if we ever need that (e.g. GCP has an outage in one region).

I'm leaving ci-operator/templates alone; hopefully those will be gone soon. I've already updated ci-tools with openshift/ci-tools@00ebab17e1 (openshift/ci-tools#1527).

I still wish the end-to-end suite pulled the region out of the cluster itself, but until it does, lean on the Infrastructure status like we've been doing for AWS since bf0a271 (#2507).

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 wking deleted the gcp-region-from-boskos-lease branch April 15, 2021 21:03
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. lgtm Indicates that a PR is ready to be merged. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants