MCO: add OKD tests for release-4.6 and release-4.7 branches

[vrutkovs]

Make sure OKD images are tested and promoted on 4.6/4.7 branch PRs.

Replaces #12615

[vrutkovs]

/cc @sinnykumari

[sinnykumari]

ah, I started working on fixing the okd related changes sometime back. Since you have already created a new pr, i will drop okd related commit 9016a5d from openshift/machine-config-operator#2145

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/machine-config-operator/release-4.7/okd-e2e-aws	24793ca	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.7/okd-e2e-upgrade	24793ca	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.7/okd-e2e-gcp-op	24793ca	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/master/okd-e2e-gcp-op	24793ca	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/master/okd-e2e-aws	24793ca	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/master/okd-e2e-upgrade	24793ca	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.6/okd-e2e-gcp-op	24793ca	link	/test pj-rehearse
ci/rehearse/openshift/machine-config-operator/release-4.6/okd-e2e-upgrade	24793ca	link	/test pj-rehearse
ci/prow/pj-rehearse	24793ca	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.

[sinnykumari]

As vadim mentioned, okd tests in ci are failing due to OVN changes. Vadim will look at failing upgrade tests later on. This shouldn't impact regular MCO tests.

/lgtm
/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sinnykumari, vrutkovs

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]

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

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-ci-robot]

@vrutkovs: Updated the following 7 configmaps:

• job-config-4.6 configmap in namespace ci at cluster api.ci using the following files:
  • key openshift-machine-config-operator-release-4.6-postsubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6-postsubmits.yaml
  • key openshift-machine-config-operator-release-4.6-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6-presubmits.yaml
• job-config-4.6 configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-machine-config-operator-release-4.6-postsubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6-postsubmits.yaml
  • key openshift-machine-config-operator-release-4.6-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6-presubmits.yaml
• job-config-4.7 configmap in namespace ci at cluster api.ci using the following files:
  • key openshift-machine-config-operator-release-4.7-postsubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7-postsubmits.yaml
  • key openshift-machine-config-operator-release-4.7-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7-presubmits.yaml
• job-config-4.7 configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-machine-config-operator-release-4.7-postsubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7-postsubmits.yaml
  • key openshift-machine-config-operator-release-4.7-presubmits.yaml using file ci-operator/jobs/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7-presubmits.yaml
• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-machine-config-operator-master__okd.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-master__okd.yaml
• ci-operator-4.6-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-machine-config-operator-release-4.6__okd.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-release-4.6__okd.yaml
• ci-operator-4.7-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-machine-config-operator-release-4.7__okd.yaml using file ci-operator/config/openshift/machine-config-operator/openshift-machine-config-operator-release-4.7__okd.yaml

Details

In response to this:

Make sure OKD images are tested and promoted on 4.6/4.7 branch PRs.

Replaces #12615

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.