CMP-3871: Add testcase for ROSA HCP (73945) to upstream

[Anna-Koudelkova]

Testcase passed on ROSA HCP 4.20 cluster:

E2E_SKIP_FRAMEWORK_SETUP=true \
TEST_OPERATOR_NAMESPACE=openshift-compliance \
go test ./tests/e2e/rosa -v \
  -run Test73945RosaHCPSubscriptionAndNodeProfilesScan \
  -timeout 120m \
  -args \
    -root="$(pwd)" \
    -globalMan=tests/_setup/crd.yaml \
    -namespacedMan=tests/_setup/deploy_rbac.yaml \
    --platform rosa
2026/04/07 18:24:58 switching to /home/akoudelk/work_repos/CaC_compliance_op/compliance-operator directory for ROSA 73945 OLM setup
2026/04/07 18:24:59 creating namespace openshift-compliance
=== RUN   Test73945RosaHCPSubscriptionAndNodeProfilesScan
2026/04/07 18:25:07 Waiting for availability of Deployment: compliance-operator in Namespace: openshift-compliance 
2026/04/07 18:25:12 Waiting for full availability of compliance-operator deployment (0/1)
2026/04/07 18:25:17 Deployment available (1/1)
2026/04/07 18:25:28 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:33 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:38 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:43 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:48 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:53 ProfileBundle ready (VALID)
2026/04/07 18:25:59 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:04 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:09 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:14 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:18 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:24 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:29 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:33 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:39 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:44 ProfileBundle ready (VALID)
2026/04/07 18:26:51 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: LAUNCHING
2026/04/07 18:26:55 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:00 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:05 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:11 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:16 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:21 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:26 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:31 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: AGGREGATING
2026/04/07 18:27:36 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: AGGREGATING
2026/04/07 18:27:41 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: AGGREGATING
2026/04/07 18:27:46 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: AGGREGATING
2026/04/07 18:27:56 ComplianceScan ready (DONE)
2026/04/07 18:28:01 ComplianceScan ready (DONE)
2026/04/07 18:28:01 All scans in ComplianceSuite have finished (test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945)
--- PASS: Test73945RosaHCPSubscriptionAndNodeProfilesScan (188.57s)
PASS
ok  	github.com/ComplianceAsCode/compliance-operator/tests/e2e/rosa	189.247s

[openshift-ci-robot]

@Anna-Koudelkova: This pull request references CMP-3871 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.

Details

In response to this:

Testcase passed on ROSA HCP 4.20 cluster:

E2E_SKIP_FRAMEWORK_SETUP=true \
TEST_OPERATOR_NAMESPACE=openshift-compliance \
go test ./tests/e2e/rosa -v \
 -run Test73945RosaHCPSubscriptionAndNodeProfilesScan \
 -timeout 120m \
 -args \
   -root="$(pwd)" \
   -globalMan=tests/_setup/crd.yaml \
   -namespacedMan=tests/_setup/deploy_rbac.yaml \
   --platform rosa
2026/04/07 18:24:58 switching to /home/akoudelk/work_repos/CaC_compliance_op/compliance-operator directory for ROSA 73945 OLM setup
2026/04/07 18:24:59 creating namespace openshift-compliance
=== RUN   Test73945RosaHCPSubscriptionAndNodeProfilesScan
2026/04/07 18:25:07 Waiting for availability of Deployment: compliance-operator in Namespace: openshift-compliance 
2026/04/07 18:25:12 Waiting for full availability of compliance-operator deployment (0/1)
2026/04/07 18:25:17 Deployment available (1/1)
2026/04/07 18:25:28 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:33 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:38 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:43 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:48 waiting ProfileBundle ocp4 to become VALID (PENDING)
2026/04/07 18:25:53 ProfileBundle ready (VALID)
2026/04/07 18:25:59 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:04 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:09 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:14 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:18 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:24 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:29 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:33 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:39 waiting ProfileBundle rhcos4 to become VALID (PENDING)
2026/04/07 18:26:44 ProfileBundle ready (VALID)
2026/04/07 18:26:51 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: LAUNCHING
2026/04/07 18:26:55 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:00 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:05 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:11 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:16 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:21 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:26 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: RUNNING
2026/04/07 18:27:31 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: AGGREGATING
2026/04/07 18:27:36 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: AGGREGATING
2026/04/07 18:27:41 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: AGGREGATING
2026/04/07 18:27:46 waiting until suite test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945 reaches target status 'DONE'. Current status: AGGREGATING
2026/04/07 18:27:56 ComplianceScan ready (DONE)
2026/04/07 18:28:01 ComplianceScan ready (DONE)
2026/04/07 18:28:01 All scans in ComplianceSuite have finished (test73945-rosa-h-c-p-subscription-and-node-profiles-scan-73945)
--- PASS: Test73945RosaHCPSubscriptionAndNodeProfilesScan (188.57s)
PASS
ok  	github.com/ComplianceAsCode/compliance-operator/tests/e2e/rosa	189.247s

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Anna-Koudelkova

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Anna-Koudelkova]

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

[github-actions]

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:1165-e0a9d162c4427ff5d8c4885bd4df01c423070985

[openshift-ci]

@Anna-Koudelkova: 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/e2e-rosa	e0a9d16	link	true	/test e2e-rosa
ci/prow/e2e-aws-parallel	e0a9d16	link	true	/test e2e-aws-parallel

Full PR test history. Your PR dashboard.

Details

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.