Removed the next set of deprecated template tests (public-cloud)

[hector-vido]

No description provided.

[hector-vido]

/retest ci/prow/config

[openshift-ci]

@hector-vido: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test app-ci-config-dry
• /test boskos-config
• /test boskos-config-generation
• /test build01-dry
• /test build02-dry
• /test build03-dry
• /test build04-dry
• /test build05-dry
• /test build09-dry
• /test build10-dry
• /test build11-dry
• /test check-gh-automation
• /test check-gh-automation-tide
• /test ci-operator-config
• /test ci-operator-config-metadata
• /test ci-operator-registry
• /test ci-secret-bootstrap-config-validation
• /test ci-testgrid-allow-list
• /test clusterimageset-validate
• /test config
• /test core-valid
• /test deprecate-templates
• /test generated-config
• /test generated-dashboards
• /test hosted-mgmt-dry
• /test image-mirroring-config-validation
• /test jira-lifecycle-config
• /test openshift-image-mirror-mappings
• /test ordered-prow-config
• /test owners
• /test pr-reminder-config
• /test prow-config
• /test prow-config-filenames
• /test prow-config-semantics
• /test pylint
• /test release-config
• /test release-controller-config
• /test secret-generator-config-valid
• /test services-valid
• /test stackrox-stackrox-stackrox-stackrox-check
• /test step-registry-metadata
• /test step-registry-shellcheck
• /test sync-rover-groups
• /test vsphere02-dry
• /test yamllint

The following commands are available to trigger optional jobs:

• /test check-cluster-profiles-config

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-release-check-gh-automation-tide
• pull-ci-openshift-release-master-boskos-config-generation
• pull-ci-openshift-release-master-ci-testgrid-allow-list
• pull-ci-openshift-release-master-config
• pull-ci-openshift-release-master-core-valid
• pull-ci-openshift-release-master-deprecate-templates
• pull-ci-openshift-release-master-generated-config
• pull-ci-openshift-release-master-ordered-prow-config
• pull-ci-openshift-release-master-owners
• pull-ci-openshift-release-master-prow-config
• pull-ci-openshift-release-master-prow-config-semantics
• pull-ci-openshift-release-master-release-config
• pull-ci-openshift-release-master-release-controller-config
• pull-ci-openshift-release-openshift-image-mirror-mappings
• pull-ci-openshift-release-yamllint

Details

In response to this:

/retest ci/prow/config

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.

[hector-vido]

/retest

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@hector-vido: 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 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.

[openshift-ci]

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

[smg247]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hector-vido, smg247

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/cluster-etcd-operator/OWNERS [hector-vido,smg247]
• ci-operator/config/openshift/installer/OWNERS [hector-vido,smg247]
• ci-operator/config/openshift/machine-config-operator/OWNERS [hector-vido,smg247]
• ci-operator/config/openshift/origin/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift-priv/cluster-etcd-operator/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift-priv/installer/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift-priv/machine-config-operator/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift-priv/origin/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift/cluster-etcd-operator/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift/installer/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift/machine-config-operator/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift/origin/OWNERS [hector-vido,smg247]
• ci-operator/jobs/openshift/release/OWNERS [hector-vido,smg247]
• core-services/prow/02_config/OWNERS [hector-vido,smg247]
• core-services/release-controller/_releases/OWNERS [hector-vido,smg247]
• core-services/template-deprecation/OWNERS [hector-vido,smg247]

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

[openshift-ci]

@hector-vido: Updated the plugins configmap in namespace ci at cluster app.ci using the following files:

• key plugins.yaml using file core-services/prow/02_config/_plugins.yaml

Details

In response to this:

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.