[release-4.7] Bug 1959009: Use DeploymentAvailable instead of custom test for CSV status.

[benluddy]

This is an automated a manual cherry-pick of #2125

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy

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:

• OWNERS [benluddy]

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

[openshift-ci]

@benluddy: This pull request references Bugzilla bug 1959009, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.7.z) matches configured target release for branch (4.7.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1945443 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 1945443 targets the "4.8.0" release, which is one of the valid target releases: 4.8.0
• bug has dependents

Requesting review from QA contact:
/cc @jianzhangbjz

In response to this:

[release-4.7] Bug 1959009: Use DeploymentAvailable instead of custom test for CSV status.

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.

[openshift-ci]

@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: jianzhangbjz.

Note that only operator-framework members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@benluddy: This pull request references Bugzilla bug 1959009, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.7.z) matches configured target release for branch (4.7.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1945443 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 1945443 targets the "4.8.0" release, which is one of the valid target releases: 4.8.0
• bug has dependents

Requesting review from QA contact:
/cc @jianzhangbjz

In response to this:

[release-4.7] Bug 1959009: Use DeploymentAvailable instead of custom test for CSV status.

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.

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.

[benluddy]

/cherry-pick release-4.6

[openshift-cherrypick-robot]

@benluddy: once the present PR merges, I will cherry-pick it on top of release-4.6 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.6

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.

[timflannagan]

/retest
/lgtm

[openshift-ci]

@benluddy: All pull requests linked via external trackers have merged:

• operator-framework/operator-lifecycle-manager#2151

Bugzilla bug 1959009 has been moved to the MODIFIED state.

In response to this:

[release-4.7] Bug 1959009: Use DeploymentAvailable instead of custom test for CSV status.

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.

[openshift-cherrypick-robot]

@benluddy: #2151 failed to apply on top of branch "release-4.6":

Applying: Use DeploymentAvailable instead of custom test for CSV status.
Using index info to reconstruct a base tree...
M	deploy/ocp/values.yaml
M	deploy/upstream/values.yaml
M	manifests/0000_50_olm_15-packageserver.clusterserviceversion.yaml
M	pkg/controller/operators/olm/operator_test.go
M	test/e2e/csv_e2e_test.go
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/csv_e2e_test.go
CONFLICT (content): Merge conflict in test/e2e/csv_e2e_test.go
Auto-merging pkg/controller/operators/olm/operator_test.go
Auto-merging manifests/0000_50_olm_15-packageserver.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in manifests/0000_50_olm_15-packageserver.clusterserviceversion.yaml
Auto-merging deploy/upstream/values.yaml
Auto-merging deploy/ocp/values.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Use DeploymentAvailable instead of custom test for CSV status.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.6

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.