OCPQE-31377: add hcp step based on openshift-test

[kuiwang02]

/cc @Xia-Zhao-rh

Summary

Add new step registry component openshift-extended-olm-test-hcp for running OLM tests on HCP (Hosted Control Plane) clusters like ROSA HCP.

Motivation

HCP clusters (ROSA HCP, HyperShift) do not have Machine CRDs since the control plane is managed externally. The existing openshift-e2e-test step includes machine/node count validation that fails on HCP clusters with:

error: the server doesn't have a resource type "machines"

This new step removes the Machine API dependency checks while preserving all other test functionality.

Changes

Created new step: ci-operator/step-registry/openshift-extended/olm-test/hcp/

Key differences from standard openshift-e2e-test step:

• ✅ Skips machine/node count matching validation (lines 148-150)
• ✅ Directly validates node readiness without checking Machine CRDs
• ✅ AWS-only support (designed for ROSA HCP clusters)
• ✅ Maintains all other functionality: cluster stability checks, test execution, sippy integration

What's removed:

• Machine API resource checks (kubectl get machines)
• GCP-specific configurations (not applicable to ROSA HCP)

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@kuiwang02: no rehearsable tests are affected by this change

[kuiwang02]

/verified by @kuiwang02

[openshift-ci-robot]

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

Details

In response to this:

/verified by @kuiwang02

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]

@kuiwang02: This pull request references OCPQE-31377 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:

/cc @Xia-Zhao-rh

Summary

Add new step registry component openshift-extended-olm-test-hcp for running OLM tests on HCP (Hosted Control Plane) clusters like ROSA HCP.

Motivation

HCP clusters (ROSA HCP, HyperShift) do not have Machine CRDs since the control plane is managed externally. The existing openshift-e2e-test step includes machine/node count validation that fails on HCP clusters with:

error: the server doesn't have a resource type "machines"

This new step removes the Machine API dependency checks while preserving all other test functionality.

Changes

Created new step: ci-operator/step-registry/openshift-extended/olm-test/hcp/

Key differences from standard openshift-e2e-test step:

• ✅ Skips machine/node count matching validation (lines 148-150)
• ✅ Directly validates node readiness without checking Machine CRDs
• ✅ AWS-only support (designed for ROSA HCP clusters)
• ✅ Maintains all other functionality: cluster stability checks, test execution, sippy integration

What's removed:

• Machine API resource checks (kubectl get machines)
• GCP-specific configurations (not applicable to ROSA HCP)

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.

[Xia-Zhao-rh]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kuiwang02, Xia-Zhao-rh

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:

• ci-operator/step-registry/openshift-extended/olm-test/OWNERS [Xia-Zhao-rh,kuiwang02]

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

[openshift-ci]

@kuiwang02: all tests passed!

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.