ci-operator/openshift/os: Remove C9S jobs from 4.16

[travier]

Those test jobs only make sense on the main development branch.

[LorbusChris]

OKD has two release streams: stable (== 4.16) and next (== 4.17). So I think these tests should still be run somewhere for 4.16

[travier]

OKD has two release streams: stable (== 4.16) and next (== 4.17). So I think these tests should still be run somewhere for 4.16

SCOS should be built only once from the master branch and then specialized for OKD versions. It does not make sense to build SCOS based on older OCP.

/pj-rehearse skip

[openshift-ci-robot]

@travier: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@travier: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-os-release-4.16-images	openshift/os	presubmit	Presubmit changed
pull-ci-openshift-os-release-4.16-rhcos-9-build-test-metal	openshift/os	presubmit	Ci-operator config changed
pull-ci-openshift-os-release-4.16-rhcos-9-build-test-qemu	openshift/os	presubmit	Ci-operator config changed
pull-ci-openshift-os-release-4.16-validate	openshift/os	presubmit	Ci-operator config changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 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 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

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.

[travier]

/pj-rehearse skip

[openshift-ci-robot]

@travier: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[HuijingHei]

/lgtm

[c4rt0]

lgtm

[travier]

This part is automatically generated from make update so I never looked at it :)

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: c4rt0, HuijingHei, travier

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/os/OWNERS [HuijingHei,c4rt0,travier]
• ci-operator/jobs/openshift/os/OWNERS [HuijingHei,c4rt0,travier]

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

[openshift-ci]

@travier: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[jlebon]

OKD has two release streams: stable (== 4.16) and next (== 4.17). So I think these tests should still be run somewhere for 4.16

SCOS should be built only once from the master branch and then specialized for OKD versions. It does not make sense to build SCOS based on older OCP.

I think the new c9s variant added in openshift/os#1445 will make this really clear because you would then take this OCP/OKD-agnostic bootable container image and derive from it multiple times (once per supported OKD version). Those base composes don't consume the c9s-sig-cloud-okd repo.