OKD: update FCOS testing jobs

[vrutkovs]

FCOS testing stream is being tested with OKD 4.13, FCOS stable stream is tested with OKD 4.12

[openshift-ci-robot]

@vrutkovs: the following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-installer-release-4.12-okd-e2e-aws-ovn-stable-stream	N/A	periodic	Periodic changed
periodic-ci-openshift-installer-release-4.13-okd-e2e-aws-ovn-testing-stream	N/A	periodic	Periodic changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse refresh to get an updated list of affected jobs (useful if you have new pushes to the branch)

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[vrutkovs]

/pj-rehearse

[vrutkovs]

/hold

openshift/installer#6487 will include "registries.conf permission fix"

[vrutkovs]

/pj-rehearse

[vrutkovs]

/pj-rehearse periodic-ci-openshift-installer-release-4.12-okd-e2e-aws-ovn-stable-stream

[vrutkovs]

/hold cancel
/pj-rehearse ack

[vrutkovs]

/cc patrickdillon jhixson74

[jhixson74]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhixson74, 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/installer/OWNERS [jhixson74]
• ci-operator/jobs/openshift/installer/OWNERS [jhixson74]

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

[openshift-ci]

@vrutkovs: all tests passed!

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.

[openshift-ci]

@vrutkovs: Updated the following 5 configmaps:

• ci-operator-4.11-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-installer-release-4.11__okd.yaml using file ci-operator/config/openshift/installer/openshift-installer-release-4.11__okd.yaml
• ci-operator-4.12-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-installer-release-4.12__okd.yaml using file ci-operator/config/openshift/installer/openshift-installer-release-4.12__okd.yaml
• ci-operator-4.13-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-installer-release-4.13__okd.yaml using file ci-operator/config/openshift/installer/openshift-installer-release-4.13__okd.yaml
• job-config-4.12 configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-installer-release-4.12-periodics.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-release-4.12-periodics.yaml
• job-config-4.13 configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-installer-release-4.11-periodics.yaml using file ``
  • key openshift-installer-release-4.13-periodics.yaml using file ci-operator/jobs/openshift/installer/openshift-installer-release-4.13-periodics.yaml

Details

In response to this:

FCOS testing stream is being tested with OKD 4.13, FCOS stable stream is tested with OKD 4.12

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.