OPRUN-3963: [operator-controller]: Call OTE in the ci in order to ensure that the tests will be executed always

[camilamacedo86]

No description provided.

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-3963 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.

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-3963 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:

/hold

Until we get merged : openshift/operator-framework-operator-controller#383

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]

/hold

Until we get merged : openshift/operator-framework-operator-controller#383

[camilamacedo86]

/hold

[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-operator-controller-main-tests-extension	openshift/operator-framework-operator-controller	presubmit	Presubmit changed
pull-ci-openshift-operator-framework-operator-controller-release-4.21-tests-extension	openshift/operator-framework-operator-controller	presubmit	Presubmit 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.

[camilamacedo86]

/pj-rehearse pull-ci-openshift-operator-framework-operator-controller-main-tests-extension

[openshift-ci-robot]

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

[camilamacedo86]

/pj-rehearse pull-ci-openshift-operator-framework-operator-controller-release-4.21-tests-extension

[openshift-ci-robot]

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

[openshift-ci]

@camilamacedo86: 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.

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-3963 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.

[tmshort]

Do you need to modify the release-4.20 files, or are we considering this a part of 4.21?

[camilamacedo86]

Do you need to modify the release-4.20 files, or are we considering this a part of 4.21?

It should be from 4.21 right?
I did not cherry-pick anything and I think we will not do.

My idea is to enable the CI so that when we add the tests in a follow up we start to check the changes with it already

[camilamacedo86]

/hold cancel
/pj-rehearse ack

[openshift-ci-robot]

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

[tmshort]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, tmshort

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/operator-framework-operator-controller/OWNERS [tmshort]
• ci-operator/jobs/openshift/operator-framework-operator-controller/OWNERS [tmshort]

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

[tmshort]

If we want it to be part of 4.20, you need to also update the 4.20 files; otherwise, after we branch, it this won't be enabled in 4.20.
As of right now, it's done via the main branch, and main=release-4.20, so I think you need to add it to 4.20 as well.