Add TechPreviewNoUpgrade Periodics for GCP and VSphere

[JoelSpeed]

Following up on #19845 which prioritised the platforms being migrated to CCMs for 4.9, this adds GCP and VSphere as TechPreviewNoUpgrade release informing jobs.

For now I've included this in the 4.9 jobs but depending on when this merges, we may want to move straight to 4.10.

As of 4.10 GCP and VSphere will also have CCMs in TechPreview and as such this is important to ensure we have sufficient testing of the CCMs.

Note for vSphere, the periodics are scheduled staggered currently, by 15 minutes each. 0, 15, 30 and 45 past the hour. To avoid confusion with those, I've staggered these new ones to 2 hours earlier and on the 0th and 30th minute. This should ensure the suite has time to pass before the other periodics start and use the quota

[JoelSpeed]

/assign @deads2k

[petr-muller]

We added configs for 4.10, can you add these there as well?

• ci-operator/config/openshift/release/openshift-release-master__ci-4.10.yaml
• ci-operator/config/openshift/release/openshift-release-master__nightly-4.10.yaml

[petr-muller]

Also do the same in core-services/release-controller/_releases/release-ocp-4.10.json

[JoelSpeed]

@petr-muller I've updated this to just be 4.10, I think for now we are only really concerned for these platforms on 4.10. Will add to 4.9 at a later date if we decide that's necessary

[openshift-ci]

@JoelSpeed: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Rerun command
ci/prow/pj-rehearse-blocking	4c1b9b96acd49df88d7c9ee97cfa4e0a8f90fbbc	link	/test pj-rehearse-blocking
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.9-e2e-vsphere-techpreview	4c1b9b96acd49df88d7c9ee97cfa4e0a8f90fbbc	link	/test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.9-e2e-gcp-techpreview-serial	4c1b9b96acd49df88d7c9ee97cfa4e0a8f90fbbc	link	/test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere-techpreview-serial	f3cdb6b	link	/test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere-techpreview	f3cdb6b	link	/test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-gcp-techpreview	f3cdb6b	link	/test pj-rehearse
ci/rehearse/periodic-ci-openshift-release-master-ci-4.10-e2e-gcp-techpreview-serial	f3cdb6b	link	/test pj-rehearse
ci/prow/pj-rehearse	f3cdb6b	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.

[JoelSpeed]

The tests are failing for two reasons, one is openshift/origin#26449, the other is a lack of a 4.10 nightly. Will try and run the rehearsals again once these two issues are resolved

[petr-muller]

@JoelSpeed I think it's fine to merge the jobs despite the failures. They will simply start giving signal once these preconditions start to hold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, 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:

• ci-operator/config/openshift/release/OWNERS [petr-muller]
• ci-operator/jobs/openshift/release/OWNERS [petr-muller]
• ci-operator/step-registry/openshift/e2e/gcp/OWNERS [petr-muller]
• ci-operator/step-registry/openshift/e2e/vsphere/OWNERS [petr-muller]
• core-services/release-controller/OWNERS [petr-muller]

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

[openshift-ci]

@JoelSpeed: Updated the following 3 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-release-master__ci-4.10.yaml using file ci-operator/config/openshift/release/openshift-release-master__ci-4.10.yaml
  • key openshift-release-master__nightly-4.10.yaml using file ci-operator/config/openshift/release/openshift-release-master__nightly-4.10.yaml
• job-config-master configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-release-master-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-master-periodics.yaml
• step-registry configmap in namespace ci at cluster app.ci using the following files:
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/techpreview/OWNERS
  • key openshift-e2e-gcp-techpreview-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/techpreview/openshift-e2e-gcp-techpreview-workflow.metadata.json
  • key openshift-e2e-gcp-techpreview-workflow.yaml using file ci-operator/step-registry/openshift/e2e/gcp/techpreview/openshift-e2e-gcp-techpreview-workflow.yaml
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/techpreview/serial/OWNERS
  • key openshift-e2e-gcp-techpreview-serial-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/gcp/techpreview/serial/openshift-e2e-gcp-techpreview-serial-workflow.metadata.json
  • key openshift-e2e-gcp-techpreview-serial-workflow.yaml using file ci-operator/step-registry/openshift/e2e/gcp/techpreview/serial/openshift-e2e-gcp-techpreview-serial-workflow.yaml
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/vsphere/techpreview/OWNERS
  • key openshift-e2e-vsphere-techpreview-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/vsphere/techpreview/openshift-e2e-vsphere-techpreview-workflow.metadata.json
  • key openshift-e2e-vsphere-techpreview-workflow.yaml using file ci-operator/step-registry/openshift/e2e/vsphere/techpreview/openshift-e2e-vsphere-techpreview-workflow.yaml
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/vsphere/techpreview/serial/OWNERS
  • key openshift-e2e-vsphere-techpreview-serial-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/vsphere/techpreview/serial/openshift-e2e-vsphere-techpreview-serial-workflow.metadata.json
  • key openshift-e2e-vsphere-techpreview-serial-workflow.yaml using file ci-operator/step-registry/openshift/e2e/vsphere/techpreview/serial/openshift-e2e-vsphere-techpreview-serial-workflow.yaml

Details

In response to this:

Following up on #19845 which prioritised the platforms being migrated to CCMs for 4.9, this adds GCP and VSphere as TechPreviewNoUpgrade release informing jobs.

For now I've included this in the 4.9 jobs but depending on when this merges, we may want to move straight to 4.10.

As of 4.10 GCP and VSphere will also have CCMs in TechPreview and as such this is important to ensure we have sufficient testing of the CCMs.

Note for vSphere, the periodics are scheduled staggered currently, by 15 minutes each. 0, 15, 30 and 45 past the hour. To avoid confusion with those, I've staggered these new ones to 2 hours earlier and on the 0th and 30th minute. This should ensure the suite has time to pass before the other periodics start and use the quota

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.