CMP-3846: Add test for successful compliance operator deletion (54055)#1007
CMP-3846: Add test for successful compliance operator deletion (54055)#1007taimurhafeez wants to merge 3 commits intoComplianceAsCode:masterfrom
Conversation
|
@taimurhafeez: This pull request references CMP-3846 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.21.0" version, but no target version was set. DetailsIn 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. |
|
Hi @taimurhafeez. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
rhmdnd
left a comment
There was a problem hiding this comment.
Looking good, and this is a perfect usecase for the tearDown phase.
Only minor comments on the test ID and the commented out log statement.
|
/retest |
1 similar comment
|
/retest |
|
This error(seems unrelated to the change) is strange. Rerun the job to see whether it reproduce again. |
@xiaojiey I tested it again and did not encounter the error. I ran on 4.20 aws. |
|
I think this looks good and the failure seems unrelated. I'm chasing down the |
|
/retest |
|
Adding doc approval since this is test-only. |
|
I wonder if this needs to be rebased to get EC testing to pass? |
|
@taimurhafeez: This pull request references CMP-3846 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.22.0" version, but no target version was set. DetailsIn 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. |
|
🤖 To deploy this PR, run the following command: |
rhmdnd
left a comment
There was a problem hiding this comment.
Oops - wrong button. Approved.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhmdnd, taimurhafeez The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Serial failure is unrelated and we're attempting to fix in #1100. Rosa failure is unrelated. |
|
New changes are detected. LGTM label has been removed. |
|
🤖 To deploy this PR, run the following command: |
|
@taimurhafeez: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Add verification that the compliance operator namespace deletion completes successfully during test teardown, ensuring the operator can be deleted cleanly without resources getting stuck in a terminating state.
It has been integrated into tear-down phase after any test. For instance, it can be checked by running any test such as
make e2e-parallel E2E_GO_TEST_FLAGS="-v -run TestScanProducesRemediations"expected output on OCP 4.21: