Skip to content

[release-4.19] OCPBUGS-78545: Skip oauth test for external control plane topology#30887

Open
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-30200-to-release-4.19
Open

[release-4.19] OCPBUGS-78545: Skip oauth test for external control plane topology#30887
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-30200-to-release-4.19

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #30200

/assign alebedev87

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 <vudinh@outlook.com>
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug OCPBUGS-60593 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":[],"errors":{"rankBeforeIssue":"expected Object","rankAfterIssue":"expected Object"}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.
/retitle [release-4.19] : Skip oauth test for external control plane topology

Details

In response to this:

This is an automated cherry-pick of #30200

/assign alebedev87

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.

@coderabbitai
Copy link

coderabbitai bot commented Mar 16, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bfe6272d-17b3-4452-8921-11f0291e58d8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot changed the title [release-4.19] OCPBUGS-60593: Skip oauth test for external control plane topology [release-4.19] : Skip oauth test for external control plane topology Mar 16, 2026
@openshift-ci openshift-ci bot requested review from ibihim and p0lyn0mial March 16, 2026 16:44
@alebedev87
Copy link
Contributor

/retitle [release-4.19] OCPBUGS-78545: Skip oauth test for external control plane topology

@openshift-ci openshift-ci bot changed the title [release-4.19] : Skip oauth test for external control plane topology [release-4.19] OCPBUGS-78545: Skip oauth test for external control plane topology Mar 16, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 16, 2026
@openshift-ci-robot
Copy link

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-78025 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-78025 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
  • bug has dependents

Requesting review from QA contact:
/cc @xingxingxia

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

Details

In response to this:

This is an automated cherry-pick of #30200

/assign alebedev87

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 March 16, 2026 16:48
Copy link
Contributor

@alebedev87 alebedev87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: alebedev87, openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign dgoodwin 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

@alebedev87
Copy link
Contributor

/assign @everettraven

For an approval.

@melvinjoseph86
Copy link
Contributor

/assign @xingxingxia for QE verification

@melvinjoseph86
Copy link
Contributor

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

@melvinjoseph86: GitHub didn't allow me to assign the following users: for, QE, verification.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign @xingxingxia for QE verification

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

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

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

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ca023980-215b-11f1-84c2-9e496d6ed361-0

@alebedev87
Copy link
Contributor

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

@openshift-cherrypick-robot: The following test 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-aws-ovn-edge-zones 25f154d link true /test e2e-aws-ovn-edge-zones

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.

@melvinjoseph86
Copy link
Contributor

/test e2e-aws-ovn-edge-zones

@melvinjoseph86
Copy link
Contributor

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

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

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

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/98fd53f0-21a7-11f1-807c-a23257fa29d1-0

@xingxingxia
Copy link

It is true that HCP doesn't have co/authentication. So, obviously, based on previous backport's test, adding directly:
/verified by @xingxingxia

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 17, 2026
@openshift-ci-robot
Copy link

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

Details

In response to this:

It is true that HCP doesn't have co/authentication. So, obviously, based on previous backport's test, adding directly:
/verified by @xingxingxia

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.

@melvinjoseph86
Copy link
Contributor

/test e2e-aws-ovn-edge-zones

@melvinjoseph86
Copy link
Contributor

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

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

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

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bc843f50-21ca-11f1-85db-5b60818213a9-0

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. 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.

7 participants