OCPBUGS-62753: for incompatible test add func to wait SA creation

[camilamacedo86]

No description provided.

[openshift-ci-robot]

@camilamacedo86: This pull request explicitly references no jira issue.

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 Jira Issue OCPBUGS-62753, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

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]

@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/openshift-e2e-aws-techpreview	3b10938	link	false	/test openshift-e2e-aws-techpreview
ci/prow/okd-scos-e2e-aws-ovn	3b10938	link	false	/test okd-scos-e2e-aws-ovn

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.

[tmshort]

ok-scos-e2e-aws-ovn is failing due to:

error: couldn't retrieve test suites: failed to extract test binaries: encountered errors while extracting binaries: extracted binary at path "/tmp/home/.cache/openshift-tests/registry_build09_ci_openshift_org_ci-op-b4t8gbcf_release_sha256_5e64ae8932aaa70bbfc208578c2b429f8f81931fe7991b0cc1de0d0d371c0e99_e1de6cc44d04/cluster-openshift-controller-manager-operator-tests-ext.gz" does not exist. the src path "/usr/bin/cluster-openshift-controller-manager-operator-tests-ext.gz" doesn't exist in image "registry.build09.ci.openshift.org/ci-op-b4t8gbcf/stable@sha256:1c8201686a31daa339fea1667d701a2b399c59e1ce5e6c94881d0a3e32c479ca". note the version of origin needs to match the version of the cluster under test

The test is looking for a file that doesn't existing in an image.

[tmshort]

The techpreview tests failed due to timeout in a post-test stage.

[tmshort]

/lgtm
/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:

• DOWNSTREAM_OWNERS [tmshort]

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

[bandrade]

/verified by @bandrade
/label qe-approved

[openshift-ci-robot]

@bandrade: This PR has been marked as verified by @bandrade.

In response to this:

/verified by @bandrade
/label qe-approved

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 Jira Issue OCPBUGS-62753, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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: Jira Issue Verification Checks: Jira Issue OCPBUGS-62753
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-62753 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

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]

/cherry-pick release-4.20

[openshift-cherrypick-robot]

@camilamacedo86: #501 failed to apply on top of branch "release-4.20":

Applying: UPSTREAM: <carry>: for incompatible test add func to wait builder and deployer SA creation by OCP controller
Using index info to reconstruct a base tree...
M	openshift/tests-extension/pkg/helpers/cluster_extension.go
M	openshift/tests-extension/test/olmv1-incompatible.go
Falling back to patching base and 3-way merge...
Auto-merging openshift/tests-extension/test/olmv1-incompatible.go
CONFLICT (content): Merge conflict in openshift/tests-extension/test/olmv1-incompatible.go
Auto-merging openshift/tests-extension/pkg/helpers/cluster_extension.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 UPSTREAM: <carry>: for incompatible test add func to wait builder and deployer SA creation by OCP controller

In response to this:

/cherry-pick release-4.20

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.