OPRUN-3805: Add new job for periodics and ensure that 4.18 has periodics

[camilamacedo86]

No description provided.

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-3805 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

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 openshift-eng/jira-lifecycle-plugin repository.

[camilamacedo86]

@dtfranz, why do we have not periodics for 4.18 yet?

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: camilamacedo86
Once this PR has been reviewed and has the lgtm label, please assign joelanford 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/operator-framework-olm/OWNERS
• ci-operator/jobs/openshift/operator-framework-olm/OWNERS

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

[camilamacedo86]

/hold

up to we merge the PR: openshift/operator-framework-operator-controller#332 and openshift/operator-framework-operator-controller#320

Also, the PR to add the periodic for: #64511

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@camilamacedo86: 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-operator-framework-olm-release-4.18-periodics-images	openshift/operator-framework-olm	presubmit	Presubmit changed
periodic-ci-openshift-operator-framework-olm-release-4.18-periodics-e2e-gcp-olm	N/A	periodic	Periodic changed
periodic-ci-openshift-operator-framework-olm-release-4.17-periodics-default-catalog-consistency	N/A	periodic	Periodic changed
periodic-ci-openshift-operator-framework-olm-release-4.18-periodics-e2e-gcp-olm-flaky	N/A	periodic	Periodic changed
periodic-ci-openshift-operator-framework-olm-release-4.18-periodics-default-catalog-consistency	N/A	periodic	Periodic 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 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.

[openshift-ci]

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

Test name	Commit	Details	Required	Rerun command
ci/prow/ci-operator-config-metadata	8bf327f	link	true	/test ci-operator-config-metadata
ci/prow/ordered-prow-config	8bf327f	link	true	/test ordered-prow-config

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.

[camilamacedo86]

It is not in the right place