⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@dustman9000
Copy link
Member

@dustman9000 dustman9000 commented Jan 16, 2026

Summary

SREP-2757 / SREP-2879

This adds daily conformance testing for ROSA HCP clusters, similar to what already exists for ROSA Classic STS clusters.

  • Create rosa-aws-hcp-conformance workflow in step registry
  • Add e2e-rosa-hcp-ovn daily job for 4.19 and 4.20 nightly builds
  • Add release controller entries as informing (optional: true)

The workflow provisions ROSA HCP clusters, runs openshift-tests conformance suite, and deprovisions clusters. Uses the same test skips as ROSA Classic conformance testing.

Related Issues

  • SREP-2757 - Implement blocking CI conformance jobs for ROSA HCP
  • SREP-2879 - Create and submit PR for ROSA HCP conformance workflow

Changes

File Description
ci-operator/step-registry/rosa/aws/hcp/conformance/ New workflow directory with OWNERS and workflow definition
openshift-release-master__nightly-4.19.yaml Add e2e-rosa-hcp-ovn job
openshift-release-master__nightly-4.20.yaml Add e2e-rosa-hcp-ovn job
release-ocp-4.19.json Add rosa-hcp-conformance as informing job
release-ocp-4.20.json Add rosa-hcp-conformance as informing job
priv/release-ocp-4.19.json Add disabled priv entry
priv/release-ocp-4.20.json Add disabled priv entry

Test Plan

/cc @joshbranham @meowfaceman

@openshift-ci openshift-ci bot requested a review from joshbranham January 16, 2026 21:24
@dustman9000 dustman9000 changed the title Add ROSA HCP conformance testing for 4.19 and 4.20 SREP-2757: Add ROSA HCP conformance testing for 4.19 and 4.20 Jan 16, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 16, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 16, 2026

@dustman9000: This pull request references SREP-2757 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 epic to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

SREP-2757 / SREP-2879

This adds daily conformance testing for ROSA HCP clusters, similar to what already exists for ROSA Classic STS clusters.

  • Create rosa-aws-hcp-conformance workflow in step registry
  • Add e2e-rosa-hcp-ovn daily job for 4.19 and 4.20 nightly builds
  • Add release controller entries as informing (optional: true)

The workflow provisions ROSA HCP clusters, runs openshift-tests conformance suite, and deprovisions clusters. Uses the same test skips as ROSA Classic conformance testing.

Related Issues

  • SREP-2757 - Implement blocking CI conformance jobs for ROSA HCP
  • SREP-2879 - Create and submit PR for ROSA HCP conformance workflow

Changes

File Description
ci-operator/step-registry/rosa/aws/hcp/conformance/ New workflow directory with OWNERS and workflow definition
openshift-release-master__nightly-4.19.yaml Add e2e-rosa-hcp-ovn job
openshift-release-master__nightly-4.20.yaml Add e2e-rosa-hcp-ovn job
release-ocp-4.19.json Add rosa-hcp-conformance as informing job
release-ocp-4.20.json Add rosa-hcp-conformance as informing job
priv/release-ocp-4.19.json Add disabled priv entry
priv/release-ocp-4.20.json Add disabled priv entry

Test Plan

/cc @joshbranham @meowfaceman

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.

1 similar comment
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 16, 2026

@dustman9000: This pull request references SREP-2757 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 epic to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

SREP-2757 / SREP-2879

This adds daily conformance testing for ROSA HCP clusters, similar to what already exists for ROSA Classic STS clusters.

  • Create rosa-aws-hcp-conformance workflow in step registry
  • Add e2e-rosa-hcp-ovn daily job for 4.19 and 4.20 nightly builds
  • Add release controller entries as informing (optional: true)

The workflow provisions ROSA HCP clusters, runs openshift-tests conformance suite, and deprovisions clusters. Uses the same test skips as ROSA Classic conformance testing.

Related Issues

  • SREP-2757 - Implement blocking CI conformance jobs for ROSA HCP
  • SREP-2879 - Create and submit PR for ROSA HCP conformance workflow

Changes

File Description
ci-operator/step-registry/rosa/aws/hcp/conformance/ New workflow directory with OWNERS and workflow definition
openshift-release-master__nightly-4.19.yaml Add e2e-rosa-hcp-ovn job
openshift-release-master__nightly-4.20.yaml Add e2e-rosa-hcp-ovn job
release-ocp-4.19.json Add rosa-hcp-conformance as informing job
release-ocp-4.20.json Add rosa-hcp-conformance as informing job
priv/release-ocp-4.19.json Add disabled priv entry
priv/release-ocp-4.20.json Add disabled priv entry

Test Plan

/cc @joshbranham @meowfaceman

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
Copy link
Contributor

openshift-ci bot commented Jan 16, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dustman9000
Once this PR has been reviewed and has the lgtm label, please assign sosiouxme for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@dustman9000 dustman9000 force-pushed the add-rosa-hcp-conformance-v2 branch 3 times, most recently from f83be54 to f701ba2 Compare January 16, 2026 21:50
@dustman9000
Copy link
Member Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

This adds daily conformance testing for ROSA HCP clusters, similar to
what already exists for ROSA Classic STS clusters.

Changes:
- Create rosa-aws-hcp-conformance workflow in step registry
- Add e2e-rosa-hcp-ovn daily job for 4.19 and 4.20 nightly builds
- Add release controller entries as informing (optional: true)

The workflow provisions ROSA HCP clusters, runs openshift-tests
conformance suite, and deprovisions clusters. Uses the same test
skips as ROSA Classic conformance testing.

Related: https://issues.redhat.com/browse/SREP-2757
Related: https://issues.redhat.com/browse/SREP-2879
@dustman9000 dustman9000 force-pushed the add-rosa-hcp-conformance-v2 branch from f701ba2 to a2261f9 Compare January 16, 2026 22:26
@dustman9000
Copy link
Member Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

HCP clusters don't have the machines API on the hosted cluster, so the
standard openshift-e2e-test ref fails when trying to compare machine
count with node count. The hypershift-conformance chain has custom
logic that handles HCP clusters correctly.

Also add HOSTED_CP=true env var which the hypershift-conformance chain
uses to set the correct KUBECONFIG path.
@dustman9000
Copy link
Member Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@dustman9000
Copy link
Member Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jan 17, 2026
Skip tests that are expected to fail on ROSA HCP:
- etcd leader changes: known flaky on HCP, skipped in 18+ other workflows
- platform components priority class: HCP architecture difference
- requests but not limits: HCP architecture difference
- OLM tests: OLM not deployed by default on ROSA HCP (optional capability)
@openshift-ci-robot openshift-ci-robot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jan 17, 2026
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@dustman9000: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-release-master-nightly-4.20-e2e-rosa-hcp-ovn N/A periodic Periodic changed
periodic-ci-openshift-release-master-nightly-4.19-e2e-rosa-hcp-ovn N/A periodic Periodic changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@joshbranham
Copy link
Contributor

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@joshbranham: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2026

@dustman9000: 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/rehearse/periodic-ci-openshift-release-master-nightly-4.20-e2e-rosa-hcp-ovn e71f469 link unknown /pj-rehearse periodic-ci-openshift-release-master-nightly-4.20-e2e-rosa-hcp-ovn
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.19-e2e-rosa-hcp-ovn e71f469 link unknown /pj-rehearse periodic-ci-openshift-release-master-nightly-4.19-e2e-rosa-hcp-ovn

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants