CMP-4610: Fix scan name collision in TestTimeoutDisabledWithZeroValue - #1367
Conversation
|
@guzalv: changing LGTM is restricted to collaborators 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 kubernetes-sigs/prow repository. |
TestTimeoutDisabledWithZeroValue and TestScanSettingBindingUsesDefaultScanSetting both create ScanSettingBindings referencing the ocp4-cis Profile, causing the operator to create ComplianceScans with the same name in the same namespace. When running in parallel, the faster test's cleanup deletes the shared scan, causing the slower test to fail with "ocp4-cis not found". Use ocp4-moderate instead since this test only validates timeout behavior and does not depend on any CIS-specific checks. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3096f16 to
3b411cb
Compare
|
🤖 To deploy this PR, run the following command: |
yuumasato
changed the title
|
@yuumasato: This pull request references CMP-4610 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 task to target the "5.1.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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: guzalv, taimurhafeez, Vincent056, yuumasato 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 |
5 participants
TestTimeoutDisabledWithZeroValue and TestScanSettingBindingUsesDefaultScanSetting both create ScanSettingBindings referencing the ocp4-cis Profile, causing the operator to create ComplianceScans with the same name in the same namespace. When running in parallel, the faster test's cleanup deletes the shared scan, causing the slower test to fail with "ocp4-cis not found".
Use ocp4-moderate instead since this test only validates timeout behavior and does not depend on any CIS-specific checks.