Skip to content

Conversation

@petr-muller
Copy link
Collaborator

The ipi workflow was removed in
openshift/release#7625 and is reintroduced as
ipi-aws in openshift/release#7734 (hopefully).
So retarget the AWS test to the ipi-aws workflow, and for now delete
the GCP test because it does not have its workflow yet.

/cc @stevekuznetsov

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 17, 2020
@petr-muller
Copy link
Collaborator Author

/hold

Needs openshift/release#7734 first

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 17, 2020
@petr-muller
Copy link
Collaborator Author

/retest

The `ipi` workflow was removed in
openshift/release#7625 and is reintroduced as
`ipi-aws` in openshift/release#7734 (hopefully).
So retarget the AWS test to the `ipi-aws` workflow, and for now delete
the GCP test because it does not have its workflow yet.
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller

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:

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

@petr-muller
Copy link
Collaborator Author

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 18, 2020
@petr-muller petr-muller added the lgtm Indicates that a PR is ready to be merged. label Mar 18, 2020
@openshift-merge-robot openshift-merge-robot merged commit b8dae81 into redhat-openshift-ecosystem:master Mar 18, 2020
@openshift-ci-robot
Copy link
Collaborator

@petr-muller: Updated the following 5 configmaps:

  • ci-operator-4.5-configs configmap in namespace ci at cluster default using the following files:
    • key redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml using file ci-operator/config/redhat-operator-ecosystem/playground/redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml
  • ci-operator-4.5-configs configmap in namespace ci-stg at cluster default using the following files:
    • key redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml using file ci-operator/config/redhat-operator-ecosystem/playground/redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml
  • ci-operator-4.5-configs configmap in namespace ci at cluster app.ci using the following files:
    • key redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml using file ci-operator/config/redhat-operator-ecosystem/playground/redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml
  • ci-operator-4.5-configs configmap in namespace ci-stg at cluster app.ci using the following files:
    • key redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml using file ci-operator/config/redhat-operator-ecosystem/playground/redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml
  • ci-operator-4.5-configs configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml using file ci-operator/config/redhat-operator-ecosystem/playground/redhat-operator-ecosystem-playground-cvp-ocp-4.5.yaml
Details

In response to this:

The ipi workflow was removed in
openshift/release#7625 and is reintroduced as
ipi-aws in openshift/release#7734 (hopefully).
So retarget the AWS test to the ipi-aws workflow, and for now delete
the GCP test because it does not have its workflow yet.

/cc @stevekuznetsov

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.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants