Add a workflow to execute single node openshift e2e test on GCP

[omertuc]

Also created job that runs said workflow in the machine-config-operator
master presubmit.

The conf step has been removed, there is now conf/aws and conf/gcp
separate steps

[omertuc]

/test pj-rehearse

[omertuc]

/test pj-rehearse

[omertuc]

/test pj-rehearse

[omertuc]

/test pj-rehearse

[omertuc]

/test pj-rehearse

DNS fixed

[omertuc]

/test pj-rehearse

[omertuc]

/test pj-rehearse

[sinnykumari]

/retest

[omertuc]

/assign @abhinavdahiya @sinnykumari

[eranco74]

/lgtm

[sinnykumari]

umm, on the second thought I don't think it is essential to add e2e-gcp-single-node to be running on MCO PRs unless we want to run some cluster level tests. MCO related tests that we want to run will be covered in https://github.com/openshift/release/pull/17357/files and corresponding tests that we are adding in MCO is in openshift/machine-config-operator#2507

[omertuc]

umm, on the second thought I don't think it is essential to add e2e-gcp-single-node to be running on MCO PRs unless we want to run some cluster level tests. MCO related tests that we want to run will be covered in #17357 (files) and corresponding tests that we are adding in MCO is in openshift/machine-config-operator#2507

Followup for the record - we agreed in chat to keep the gcp sno mco job anyway

[staebler]

/assign @jstuever

[sinnykumari]

/cc @patrickdillon

[openshift-ci]

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

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/cluster-authentication-operator/master/e2e-aws-single-node	76137ba0d5f04a29427ffa407cc6a32d5a049b8c	link	/test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-single-node	76137ba0d5f04a29427ffa407cc6a32d5a049b8c	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/master/e2e-gcp-single-node	82c7ff9	link	/test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.8-e2e-aws-single-node	82c7ff9	link	/test pj-rehearse
ci/prow/pj-rehearse	82c7ff9	link	/test pj-rehearse

Full PR test history. Your PR dashboard.

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.

[patrickdillon]

/approve

[eranco74]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eranco74, omertuc, patrickdillon, sinnykumari

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/machine-config-operator/OWNERS [sinnykumari]
• ci-operator/jobs/openshift/machine-config-operator/OWNERS [sinnykumari]
• ci-operator/step-registry/openshift/e2e/aws/single-node/OWNERS [eranco74,omertuc]
• ci-operator/step-registry/openshift/e2e/gcp/OWNERS [patrickdillon]
• ci-operator/step-registry/single-node/conf/OWNERS [eranco74,omertuc]

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

[openshift-ci-robot]

@omertuc: Updated the following 3 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-machine-config-operator-master.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-master.yaml
• job-config-master configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-machine-config-operator-master-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-master-presubmits.yaml
• step-registry configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-e2e-aws-single-node-workflow.yaml using file ci-operator/step-registry/openshift/e2e/aws/single-node/openshift-e2e-aws-single-node-workflow.yaml
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/single-node/OWNERS
  • key openshift-e2e-gcp-single-node-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/single-node/openshift-e2e-gcp-single-node-workflow.metadata.json
  • key openshift-e2e-gcp-single-node-workflow.yaml using file ci-operator/step-registry/openshift/e2e/gcp/single-node/openshift-e2e-gcp-single-node-workflow.yaml
  • key OWNERS using file ci-operator/step-registry/single-node/conf/aws/OWNERS
  • key single-node-conf-commands.sh using file ``
  • key single-node-conf-aws-commands.sh using file ci-operator/step-registry/single-node/conf/aws/single-node-conf-aws-commands.sh
  • key single-node-conf-ref.metadata.json using file ``
  • key single-node-conf-aws-ref.metadata.json using file ci-operator/step-registry/single-node/conf/aws/single-node-conf-aws-ref.metadata.json
  • key single-node-conf-ref.yaml using file ``
  • key single-node-conf-aws-ref.yaml using file ci-operator/step-registry/single-node/conf/aws/single-node-conf-aws-ref.yaml
  • key OWNERS using file ci-operator/step-registry/single-node/conf/gcp/OWNERS
  • key single-node-conf-gcp-commands.sh using file ci-operator/step-registry/single-node/conf/gcp/single-node-conf-gcp-commands.sh
  • key single-node-conf-gcp-ref.metadata.json using file ci-operator/step-registry/single-node/conf/gcp/single-node-conf-gcp-ref.metadata.json
  • key single-node-conf-gcp-ref.yaml using file ci-operator/step-registry/single-node/conf/gcp/single-node-conf-gcp-ref.yaml

Details

In response to this:

Also created job that runs said workflow in the machine-config-operator
master presubmit.

The conf step has been removed, there is now conf/aws and conf/gcp
separate steps

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.