WIP: PR to test hypothesis for OCPBUGS-23744

[anik120]

Hypothesis is that if we wait for the SA, ClusterRole and ClusterRolebinding to be available before we create the packageserver CSV, it'll solve OCPBUGS-23744

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120

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:

• DOWNSTREAM_OWNERS [anik120]

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

[anik120]

/test e2e-upgrade

[openshift-ci]

@anik120: 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/test-infra repository. I understand the commands that are listed here.

[anik120]

job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded

[kuiwang02]

/payload-aggregate periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-azure-sdn-upgrade 10

[openshift-ci]

@kuiwang02: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-azure-sdn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/74e613f0-d148-11ee-8b82-e37c7fb8275b-0

[kuiwang02]

/payload-aggregate periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-azure-sdn-upgrade 10

[openshift-ci]

@kuiwang02: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-azure-sdn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7ce28930-d44f-11ee-8f47-a8b16727c906-0

[anik120]

@kuiwang02 Like @wking mentioned in the ticket, I'm not sure if that command is testing payloads that include this PR. I've done some manual testing, and it looks like it's all succeeding with this PR:

• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded
• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded
• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded
• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded
• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded
• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded
• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded
• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded
• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws succeeded

There was one test that failed:

• job test upgrade 4.14,openshift/operator-framework-olm#699 4.15 aws failed

but that was for tests not related to the packageserver.

I'm going ahead with the PR in the main branch and starting the backport process with these changes.

[anik120]

Closing in favor of #708