Skip to content

Conversation

dinhxuanvu
Copy link
Member

@dinhxuanvu dinhxuanvu commented Sep 2, 2025

For HyperShift, the control plane topology is external as control
plane components are not deployed in management cluster. As a result,
the oauth operator is unavailable and this test should be skipped.
Moving the topology check to the top before the cluster auth operator
check will ensure this test is skipped in external topology mode.

@dinhxuanvu dinhxuanvu changed the title Check for control-plane operator in hypershift for oauth test [WIP] Check for control-plane operator in hypershift for oauth test Sep 2, 2025
@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 Sep 2, 2025
@dinhxuanvu
Copy link
Member Author

/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance-serial

Copy link
Contributor

openshift-ci bot commented Sep 2, 2025

@dinhxuanvu: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/74f7ed50-8803-11f0-8764-482860b01723-0

@openshift-ci openshift-ci bot requested review from everettraven and liouk September 2, 2025 13:51
Copy link
Contributor

openshift-ci bot commented Sep 2, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

@dinhxuanvu dinhxuanvu changed the title [WIP] Check for control-plane operator in hypershift for oauth test OCPBUGS-60593: Check for control-plane operator in hypershift for oauth test Sep 3, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 3, 2025
@openshift-ci-robot
Copy link

@dinhxuanvu: This pull request references Jira Issue OCPBUGS-60593, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

In HyperShift env, cluster-authentication-operator doesn't run in management cluster. Instead, control-plane operator will handle authenication operations.

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 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 Sep 3, 2025
@dinhxuanvu
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 3, 2025
@openshift-ci-robot
Copy link

@dinhxuanvu: This pull request references Jira Issue OCPBUGS-60593, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @xingxingxia

In response to this:

/jira refresh

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 openshift-ci bot requested a review from xingxingxia September 3, 2025 14:27
@dinhxuanvu
Copy link
Member Author

@everettraven Hey Bryce, I think this PR is good to go unless you have any further comments. PTAL. Thanks.

@dinhxuanvu dinhxuanvu changed the title OCPBUGS-60593: Check for control-plane operator in hypershift for oauth test OCPBUGS-60593: Skip oauth test for external control plane topology Sep 9, 2025
@openshift-ci-robot
Copy link

@dinhxuanvu: This pull request references Jira Issue OCPBUGS-60593, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @xingxingxia

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

For HyperShift, the control plane topology is external as control
plane components are not deployed in management cluster. As a result,
the oauth operator is unavailable and this test should be skipped.
Moving the topology check to the top before the cluster auth operator
check will ensure this test is skipped in external topology mode.

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.

For HyperShift, the control plane topology is external as control
plane components are not deployed in management cluster. As a result,
the oauth operator is unavailable and this test should be skipped.
Moving the topology check to the top before the cluster auth operator
check will ensure this test is skipped in external topology mode.

Signed-off-by: Vu Dinh <[email protected]>
Copy link
Contributor

openshift-ci bot commented Sep 10, 2025

@dinhxuanvu: 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-gcp-ovn-techpreview-serial-2of2 02635e1 link false /test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-aws-ovn 02635e1 link false /test e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade 02635e1 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/verify 02635e1 link true /test verify
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 02635e1 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-serial-2of2 02635e1 link true /test e2e-aws-ovn-serial-2of2
ci/prow/okd-scos-e2e-aws-ovn 02635e1 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-edge-zones 02635e1 link false /test e2e-aws-ovn-edge-zones
ci/prow/e2e-azure 02635e1 link false /test e2e-azure
ci/prow/e2e-openstack-ovn 02635e1 link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-fips 02635e1 link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-proxy 02635e1 link false /test e2e-aws-proxy
ci/prow/e2e-hypershift-conformance 02635e1 link false /test e2e-hypershift-conformance
ci/prow/e2e-aws-ovn-serial-1of2 02635e1 link true /test e2e-aws-ovn-serial-1of2
ci/prow/e2e-aws-csi 02635e1 link false /test e2e-aws-csi
ci/prow/e2e-aws-ovn-single-node 02635e1 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-serial 02635e1 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-cgroupsv2 02635e1 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-gcp-ovn 02635e1 link true /test e2e-gcp-ovn
ci/prow/e2e-agnostic-ovn-cmd 02635e1 link false /test e2e-agnostic-ovn-cmd
ci/prow/okd-scos-images 02635e1 link true /test okd-scos-images
ci/prow/e2e-aws-disruptive 02635e1 link false /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-virtualmedia 02635e1 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 02635e1 link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout

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.

Copy link

openshift-trt bot commented Sep 10, 2025

Job Failure Risk Analysis for sha: 02635e1

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-disruptive IncompleteTests
Tests for this run (21) are below the historical average (366): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-azure IncompleteTests
Tests for this run (22) are below the historical average (3345): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-openstack-ovn IncompleteTests
Tests for this run (28) are below the historical average (2348): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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