Skip to content

Conversation

@everettraven
Copy link
Contributor

We found out that a fix for https://issues.redhat.com/browse/OCPBUGS-61432 that merged in the OpenShift Console led to a regression in the external OIDC behavior despite passing the existing suite of tests.

This is because we missed making sure that the status of both the OpenShift Console and OpenShift CLI clients are successfully reporting as Available when opting in to the External OIDC functionality.

This PR updates the testing logic to ensure both of these clients are reporting that they are available to prevent a regression related to this in the future.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 21, 2025
@everettraven
Copy link
Contributor Author

/payload-job periodic-ci-openshift-cluster-authentication-operator-release-4.21-periodics-e2e-aws-external-oidc-configure

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 21, 2025

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

  • periodic-ci-openshift-cluster-authentication-operator-release-4.21-periodics-e2e-aws-external-oidc-configure

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/41388ba0-aeaf-11f0-8d13-776c63461c71-0

Signed-off-by: Bryce Palmer <[email protected]>
@everettraven
Copy link
Contributor Author

/payload-job periodic-ci-openshift-cluster-authentication-operator-release-4.21-periodics-e2e-aws-external-oidc-configure

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 22, 2025

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

  • periodic-ci-openshift-cluster-authentication-operator-release-4.21-periodics-e2e-aws-external-oidc-configure

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0f44eef0-af6c-11f0-8b54-022f9bc74b2f-0

@liouk
Copy link
Member

liouk commented Oct 23, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, liouk

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

The pull request process is described 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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2025

@everettraven: This PR was included in a payload test run from openshift/console-operator#1058
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-cluster-authentication-operator-release-4.21-periodics-e2e-aws-external-oidc-configure

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/747dcae0-b03d-11f0-92c3-8601de7281c9-0

@everettraven everettraven changed the title oidc: ensure console and cli OIDC clients are available when enabling OIDC NO-JIRA: oidc: ensure console and cli OIDC clients are available when enabling OIDC Nov 3, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 3, 2025
@openshift-ci-robot
Copy link

@everettraven: This pull request explicitly references no jira issue.

In response to this:

We found out that a fix for https://issues.redhat.com/browse/OCPBUGS-61432 that merged in the OpenShift Console led to a regression in the external OIDC behavior despite passing the existing suite of tests.

This is because we missed making sure that the status of both the OpenShift Console and OpenShift CLI clients are successfully reporting as Available when opting in to the External OIDC functionality.

This PR updates the testing logic to ensure both of these clients are reporting that they are available to prevent a regression related to this in the future.

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.

@everettraven
Copy link
Contributor Author

/verified by @everettraven

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 3, 2025
@openshift-ci-robot
Copy link

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

In response to this:

/verified by @everettraven

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

/retest-required

Remaining retests: 0 against base HEAD 87710bd and 2 for PR HEAD 58ac6f2 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 560414a and 1 for PR HEAD 58ac6f2 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b115048 and 0 for PR HEAD 58ac6f2 in total

@openshift-ci-robot
Copy link

/hold

Revision 58ac6f2 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 4, 2025
@everettraven
Copy link
Contributor Author

/retest-required

@everettraven
Copy link
Contributor Author

/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 4, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b115048 and 2 for PR HEAD 58ac6f2 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2d22e87 and 1 for PR HEAD 58ac6f2 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4f47dc4 and 0 for PR HEAD 58ac6f2 in total

@openshift-ci-robot
Copy link

/hold

Revision 58ac6f2 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 5, 2025
@everettraven
Copy link
Contributor Author

/retest-required

@everettraven
Copy link
Contributor Author

/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 6, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 606e09f and 2 for PR HEAD 58ac6f2 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 7, 2025

@everettraven: 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-microshift 58ac6f2 link unknown /test e2e-aws-ovn-microshift

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 7, 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: 58ac6f2

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial]" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[sig-storage] [Serial] Volume metrics Ephemeral should create volume metrics with the correct BlockMode PVC ref" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[sig-storage] [Serial] Volume metrics PVC should create volume metrics in Volume Manager" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[sig-storage] [Serial] Volume metrics PVC should create volume metrics with the correct FilesystemMode PVC ref" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 58ac6f2

  • "[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial]" [Total: 5, Pass: 5, Fail: 0, Flake: 0]
  • "[sig-storage] [Serial] Volume metrics Ephemeral should create volume metrics with the correct BlockMode PVC ref" [Total: 5, Pass: 5, Fail: 0, Flake: 0]
  • "[sig-storage] [Serial] Volume metrics PVC should create volume metrics in Volume Manager" [Total: 5, Pass: 5, Fail: 0, Flake: 0]
  • "[sig-storage] [Serial] Volume metrics PVC should create volume metrics with the correct FilesystemMode PVC ref" [Total: 5, Pass: 5, Fail: 0, Flake: 0]

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.

3 participants