Revert migration

[hongkailiu]

https://coreos.slack.com/archives/CBN38N3MW/p1576792909111900

/cc @openshift/openshift-team-developer-productivity-test-platform

/hold

wait for the revert on ci-tools

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu

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:

• ci-operator/config/openshift/ci-secret-mirroring-controller/OWNERS [hongkailiu]
• ci-operator/config/openshift/origin/OWNERS [hongkailiu]
• ci-operator/jobs/openshift/origin/OWNERS [hongkailiu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[stevekuznetsov]

Will force merge this -- it will fail formatting until the generator is fixed

[openshift-ci-robot]

@hongkailiu: Updated the following 4 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
  • key openshift-ci-secret-mirroring-controller-master.yaml using file ci-operator/config/openshift/ci-secret-mirroring-controller/openshift-ci-secret-mirroring-controller-master.yaml
  • key openshift-origin-master.yaml using file ci-operator/config/openshift/origin/openshift-origin-master.yaml
• ci-operator-master-configs configmap in namespace ci at cluster default using the following files:
  • key openshift-ci-secret-mirroring-controller-master.yaml using file ci-operator/config/openshift/ci-secret-mirroring-controller/openshift-ci-secret-mirroring-controller-master.yaml
  • key openshift-origin-master.yaml using file ci-operator/config/openshift/origin/openshift-origin-master.yaml
• ci-operator-master-configs configmap in namespace ci-stg at cluster default using the following files:
  • key openshift-ci-secret-mirroring-controller-master.yaml using file ci-operator/config/openshift/ci-secret-mirroring-controller/openshift-ci-secret-mirroring-controller-master.yaml
  • key openshift-origin-master.yaml using file ci-operator/config/openshift/origin/openshift-origin-master.yaml
• job-config-master configmap in namespace ci at cluster default using the following files:
  • key openshift-origin-master-postsubmits.yaml using file ci-operator/jobs/openshift/origin/openshift-origin-master-postsubmits.yaml
  • key openshift-origin-master-presubmits.yaml using file ci-operator/jobs/openshift/origin/openshift-origin-master-presubmits.yaml

Details

In response to this:

https://coreos.slack.com/archives/CBN38N3MW/p1576792909111900

/cc @openshift/openshift-team-developer-productivity-test-platform

/hold

wait for the revert on ci-tools

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.

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/generated-config	2ebf8ae	link	/test generated-config
ci/rehearse/openshift/origin/master/e2e-conformance-k8s	2ebf8ae	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/images	2ebf8ae	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-vsphere	2ebf8ae	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/launch-vsphere	2ebf8ae	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-gcp-builds	2ebf8ae	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-gcp-image-ecosystem	2ebf8ae	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-aws-disruptive	2ebf8ae	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-aws-ovn	2ebf8ae	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-gcp-upgrade	2ebf8ae	link	/test pj-rehearse
ci/prow/pj-rehearse	2ebf8ae	link	/test pj-rehearse

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.

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/test-infra repository. I understand the commands that are listed here.