Remove old OKD jobs

[sarthakpurohit]

There are some fcos based OKD jobs lying around in some repos which are permafailing. The machine-config-operator is an example. We need to scour the release repo for these jobs and nuke the config and the jobs as well.

[openshift-ci]

Hi @sarthakpurohit. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[sarthakpurohit]

Tagging @Prashanth684 for review

[Prashanth684]

Can you run make jobs and also include the pre and postsubmit files here? it would have removed those jobs from these files as well.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sarthakpurohit
Once this PR has been reviewed and has the lgtm label, please assign deads2k, hroyrh, pablintino for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/cluster-update-keys/OWNERS
• ci-operator/config/openshift/machine-config-operator/OWNERS
• ci-operator/config/openshift/machine-os-images/OWNERS
• ci-operator/config/openshift/origin/OWNERS
• ci-operator/jobs/openshift/cluster-update-keys/OWNERS
• ci-operator/jobs/openshift/machine-config-operator/OWNERS
• ci-operator/jobs/openshift/machine-os-images/OWNERS
• ci-operator/jobs/openshift/origin/OWNERS

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

[sarthakpurohit]

@Prashanth684 missed those. Added now.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@sarthakpurohit: no rehearsable tests are affected by this change

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 list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

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.