Skip to content

Conversation

@mtulio
Copy link
Contributor

@mtulio mtulio commented Sep 10, 2025

Added binary to the OTE of a project cloud-provider-aws.

Acceptance criteria

Changes that must be tested with the OTE:

The following tests must be successful executed to validate the feature with OTE:

  • Run OTE binary on AWS: /testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#121 openshift/cluster-cloud-controller-manager-operator#391
  • Run OTE binary on GCP: /testwith openshift/origin/main/e2e-gcp-ovn openshift/cloud-provider-aws#121 openshift/cluster-cloud-controller-manager-operator#391
  • Run OTE binary on vSphere: /testwith openshift/origin/main/e2e-vsphere-ovn openshift/cloud-provider-aws#121 openshift/cluster-cloud-controller-manager-operator#391

To validate the passing scenario, we are using those conditionals:

  1. The OTE binary /usr/bin/aws-cloud-controller-manager-tests-ext.gz must be extracted by openshift-tests in the step openshift-e2e-test (query string: msg="Extracted /usr/bin/aws-cloud-controller-manager-tests-ext.gz)
  2. The OTE binary must return test count in the step. (Query string ms" binary=aws-cloud-controller-manager-tests-ext)
    • For AWS must return 7 tests. Example: msg="Listed 7 tests in 57.89931ms" binary=aws-cloud-controller-manager-tests-ext
    • For other providers must return 0 tests. Example: msg="Listed 0 tests in 52.698354ms" binary=aws-cloud-controller-manager-tests-ext
  3. The OTE binary must run successfully all tests prefixed with [cloud-provider-aws-e2] * on AWS, or just run regular e2e without any CCM tests on other providers.
  4. The execution (pass list) must have the following test count on AWS job:
  • [cloud-provider-aws-e2e] nodes total of 2 tests. (query: passed: * "[cloud-provider-aws-e2e] nodes)`
  • [cloud-provider-aws-e2e] loadbalancer total of 5 tests. (query: passed: * "[cloud-provider-aws-e2e] loadbalancer)`)

Test results:

Platform Job ID/Step Results As Expected?
aws 1986444266678784000 / step All checked Yes
vsphere 1986476792151543808 / step All passed Yes
gcp 1986497082852118528 / step WIP healthy install TBD

Related to:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 10, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 10, 2025

@mtulio: This pull request references SPLAT-2337 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.

In response to this:

Added binary to the OTE of a project cloud-provider-aws.

Related to:

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 Sep 10, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@mtulio
Copy link
Contributor Author

mtulio commented Sep 24, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

1 similar comment
@mtulio
Copy link
Contributor Author

mtulio commented Sep 24, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

@mtulio
Copy link
Contributor Author

mtulio commented Sep 25, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

level=error msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed during pre-provisioning: failed to create IAM roles: failed to create master instance profile: operation error IAM: CreateInstanceProfile, exceeded maximum number of attempts, 3, https response error StatusCode: 400, RequestID: 5387c91e-05d7-4bf5-a24c-b09dc9d8293c, api error Throttling: Rate exceeded

CI Infra issue while installing cluster / creating IAM roles (I wonder if we need a backoff/retry improvement in that part) - testing again:

@mtulio
Copy link
Contributor Author

mtulio commented Sep 25, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

1 similar comment
@mtulio
Copy link
Contributor Author

mtulio commented Sep 25, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

@mtulio mtulio marked this pull request as ready for review October 1, 2025 21:07
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 1, 2025
@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial October 1, 2025 21:07
@mtulio
Copy link
Contributor Author

mtulio commented Oct 2, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

@mtulio mtulio marked this pull request as draft October 2, 2025 03:11
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 2, 2025
@mtulio
Copy link
Contributor Author

mtulio commented Oct 2, 2025

Converting to draft, investigating issues on testwith in the original PR.

@mtulio
Copy link
Contributor Author

mtulio commented Oct 2, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

@mtulio
Copy link
Contributor Author

mtulio commented Oct 2, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

I can build the image in ccm repo using the PR openshift/cloud-provider-aws#117 , let me try again.

$ make -f openshift-hack/Makefile image 
podman build \
	--authfile /home/me/.openshift/pull-secret-202509091449.json \
	-f Dockerfile.openshift \
	-t aws-cloud-controller-manager:v1.34.0-rc.0-307-gf3ac98762 .
[1/2] STEP 1/5: FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.24-openshift-4.20 AS builder

...
Successfully tagged localhost/aws-cloud-controller-manager:v1.34.0-rc.0-307-gf3ac98762
f2d8b099969f5774d915fa9e25a9151f28a2b2608cd070f8187e9ec97f05d7c3

@mtulio
Copy link
Contributor Author

mtulio commented Oct 2, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

1 similar comment
@mtulio
Copy link
Contributor Author

mtulio commented Oct 2, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

@mtulio
Copy link
Contributor Author

mtulio commented Oct 2, 2025

The latest testwith ran correctly, with 5/7 tests failing. I just updated the CCM/OTE PR to address the issue. re-trying ^ (my last comment)

@mtulio
Copy link
Contributor Author

mtulio commented Oct 3, 2025

/testwith openshift/origin/main/e2e-aws-ovn openshift/cloud-provider-aws#117

@mtulio
Copy link
Contributor Author

mtulio commented Oct 3, 2025

something went wrong in the last rebase, I will remove the unrelated OTE commits soon in my next cycle.

@mtulio
Copy link
Contributor Author

mtulio commented Oct 3, 2025

Successful execution =)

I just converted the ccm-aws repo to ready for review with final changes. Triggering with latest version to ensure readiness after updating vedor:

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 5c72de0 and 0 for PR HEAD 3cf42fd in total

@openshift-trt
Copy link

openshift-trt bot commented Nov 12, 2025

Job Failure Risk Analysis for sha: 3cf42fd

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 IncompleteTests
Tests for this run (72) are below the historical average (3033): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 3cf42fd

  • "[cloud-provider-aws-e2e] loadbalancer CLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer CLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with target-node-labels [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should label nodes with topology network info if instance is supported [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should set zone-id topology label [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]

@openshift-ci-robot
Copy link

/hold

Revision 3cf42fd was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 12, 2025
@mtulio
Copy link
Contributor Author

mtulio commented Nov 12, 2025

I will work on #30476 to increase verbosity on OTE binary to investigate issues affecting only the job e2e-metal-ipi-ovn-ipv6.

@mtulio
Copy link
Contributor Author

mtulio commented Nov 13, 2025

/testwith openshift/origin/main/e2e-metal-ipi-ovn-ipv6 #30476 openshift/cloud-provider-aws#122

@mtulio
Copy link
Contributor Author

mtulio commented Nov 13, 2025

/testwith openshift/origin/main/e2e-aws-ovn #30476 openshift/cloud-provider-aws#122

@mtulio
Copy link
Contributor Author

mtulio commented Nov 17, 2025

/testwith openshift/origin/main/e2e-aws-ovn #30476 openshift/cloud-provider-aws#122

this one is passing. Awaiting openshift/cloud-provider-aws#122 to be fixed before asking for review here

@openshift-trt
Copy link

openshift-trt bot commented Nov 18, 2025

Job Failure Risk Analysis for sha: 3cf42fd

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 IncompleteTests
Tests for this run (22) are below the historical average (2444): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 3cf42fd

  • "[cloud-provider-aws-e2e] loadbalancer CLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer CLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with target-node-labels [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should label nodes with topology network info if instance is supported [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should set zone-id topology label [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]

@mtulio
Copy link
Contributor Author

mtulio commented Nov 18, 2025

PR openshift/cloud-provider-aws#122 merged, re-trying>

/test e2e-metal-ipi-ovn-ipv6

@openshift-trt
Copy link

openshift-trt bot commented Nov 18, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 3cf42fd

  • "[cloud-provider-aws-e2e] loadbalancer CLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer CLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with target-node-labels [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should label nodes with topology network info if instance is supported [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should set zone-id topology label [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]

@mtulio
Copy link
Contributor Author

mtulio commented Nov 19, 2025

PR openshift/cloud-provider-aws#122 merged, re-trying>

/test e2e-metal-ipi-ovn-ipv6

Per tests passing:

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 19, 2025
@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 19, 2025

@mtulio: all tests passed!

Full PR test history. Your PR dashboard.

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.

@openshift-trt
Copy link

openshift-trt bot commented Nov 19, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 3cf42fd

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[cloud-provider-aws-e2e] loadbalancer CLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[cloud-provider-aws-e2e] loadbalancer CLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[cloud-provider-aws-e2e] loadbalancer NLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with target-node-labels [Suite:openshift/conformance/parallel]" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[cloud-provider-aws-e2e] nodes should label nodes with topology network info if instance is supported [Suite:openshift/conformance/parallel]" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High - "[cloud-provider-aws-e2e] nodes should set zone-id topology label [Suite:openshift/conformance/parallel]" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 3cf42fd

  • "[cloud-provider-aws-e2e] loadbalancer CLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer CLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with target-node-labels [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should label nodes with topology network info if instance is supported [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should set zone-id topology label [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]

@openshift-trt
Copy link

openshift-trt bot commented Nov 19, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 3cf42fd

  • "[cloud-provider-aws-e2e] loadbalancer CLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer CLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with target-node-labels [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should label nodes with topology network info if instance is supported [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should set zone-id topology label [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]

1 similar comment
@openshift-trt
Copy link

openshift-trt bot commented Nov 19, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 3cf42fd

  • "[cloud-provider-aws-e2e] loadbalancer CLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer CLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB internal should be reachable with hairpinning traffic [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with default configurations [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] loadbalancer NLB should be reachable with target-node-labels [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should label nodes with topology network info if instance is supported [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[cloud-provider-aws-e2e] nodes should set zone-id topology label [Suite:openshift/conformance/parallel]" [Total: 4, Pass: 4, Fail: 0, Flake: 0]

@openshift-merge-bot openshift-merge-bot bot merged commit 24a0dee into openshift:main Nov 20, 2025
23 of 25 checks passed
@mtulio mtulio deleted the SPLAT-2337-ote-ccm-aws branch November 24, 2025 16:06
@mtulio mtulio restored the SPLAT-2337-ote-ccm-aws branch November 24, 2025 17:51
mtulio added a commit to mtulio/release that referenced this pull request Nov 25, 2025
Enalbe presubmit jobs on origin, CCCMO, and cloud-provider-aws
to validate conformance jobs on techpreview using hypershift,
ensuring upstream CCM-AWS e2e tests recently introduced is executed
correctly in hypershift workload clusters.

Ref openshift/origin#30235
mtulio added a commit to mtulio/release that referenced this pull request Nov 25, 2025
Enalbe presubmit jobs on origin, CCCMO, and cloud-provider-aws
to validate conformance jobs on techpreview using hypershift,
ensuring upstream CCM-AWS e2e tests recently introduced is executed
correctly in hypershift workload clusters.

Ref openshift/origin#30235
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants