OCPBUGS-56892: Console can only show user name instead of full name as the display name #15522

Leo6Leo · 2025-09-22T17:50:06Z

Description

After logging in with Google OAuth OIDC, the Console can only show username instead of full name as the display name on the top right corner in the console.

Step to test out the changes

Have a cluster that configure the Google OIDC login. If you don't have one, you can follow the instructions I wrote in the Appendix which locates at the bottom of this PR description.
Choose Google-OpenID-Connect as your login option and login with your google account

After your success login, you will see on the right top corner is displaying your full name, instead of your email address.

Special Note

Thanks to @logonoff for the discussion on what would be the better way to resolve this issue.

Appendix: How to configure Google OAuth on your cluster for testing purpose

Prerequisites

Before you begin, you'll need:

Administrator access to your OpenShift cluster using the oc and kubectl CLI.
A Google Cloud project with an OAuth 2.0 Client ID and Client Secret created. If you need to create one, follow Google's official documentation.

Step 1: Create the Google Client Secret in OpenShift

First, create a k8s secret in the openshift-config namespace to securely store your Google OAuth client secret. This prevents storing sensitive values directly in the main cluster configuration.

Replace <your-google-client-secret> with the actual client secret from your Google Cloud project.

oc create secret generic google-secret \
  --from-literal=clientSecret=<your-google-client-secret> \
  -n openshift-config

Step 2: Configure the Cluster OAuth Identity Provider

Next, edit the cluster-wide OAuth configuration to add Google as an identity provider.

oc edit oauth cluster

Replace with the Client ID from your Google Cloud project.

spec:
  identityProviders:
  - name: Google                 # This is the name that will appear on the login page
    mappingMethod: claim
    type: OpenID
    openID:
      clientID: <your-google-client-id>
      clientSecret:
        name: google-secret      # The name of the secret you created in Step 1
      extraScopes:
      - email
      - profile
      issuer: https://accounts.google.com
      claims:
        preferredUsername:
        - email
        name:
        - name
        email:
        - email

Save and close the editor. Then wait until the authentication operator finish reconciling.

Step 3: Get the redirect_uri and Update Google Cloud

This is a crucial step. OpenShift generates a unique callback URL that Google needs to know about for security.

Open your OpenShift cluster's web console in a browser. You should now see the "Google" login option.
Click the Google login button. You will likely be redirected to a Google error page saying something like "Error 400: redirect_uri_mismatch". This is expected!
Copy the entire URL from your browser's address bar. Find the redirect_uri parameter within that URL. It will look something like this:
https://oauth-openshift.apps../oauth2callback/Google
Go to your project in the Google Cloud Console.
Navigate to your OAuth 2.0 Client ID.
Under the "Authorized redirect URIs" section, click "ADD URI" and paste the full redirect_uri you copied.
Click Save.
Login with your google account again and you will see it works!

…ation

…hook in telemetry and masthead components

… data retrieval and dispatch behavior

openshift-ci-robot · 2025-09-22T17:50:13Z

@Leo6Leo: This pull request references Jira Issue OCPBUGS-56892, 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.

Details

In response to this:

Description

After logging in with Google OAuth OIDC, the Console can only show username instead of full name as the display name on the top right corner in the console.

Step to test out the changes

Have a cluster that configure the Google OIDC login. If you don't have one, you can follow the instructions I wrote in the Appendix which locates at the bottom of this PR description.

Choose Google-OpenID-Connect as your login option and login with your google account

After your success login, you will see on the right top corner is displaying your full name, instead of your email address.

Special Note

Thanks to @logonoff for the discussion on what would be the better way to resolve this issue.

Appendix: How to configure Google OAuth on your cluster for testing purpose

Prerequisites

Before you begin, you'll need:

Administrator access to your OpenShift cluster using the oc and kubectl CLI.

A Google Cloud project with an OAuth 2.0 Client ID and Client Secret created. If you need to create one, follow Google's official documentation.

Step 1: Create the Google Client Secret in OpenShift

First, create a k8s secret in the openshift-config namespace to securely store your Google OAuth client secret. This prevents storing sensitive values directly in the main cluster configuration.

Replace <your-google-client-secret> with the actual client secret from your Google Cloud project.
oc create secret generic google-secret \
 --from-literal=clientSecret=<your-google-client-secret> \
 -n openshift-config
Step 2: Configure the Cluster OAuth Identity Provider

Next, edit the cluster-wide OAuth configuration to add Google as an identity provider.
oc edit oauth cluster
Replace with the Client ID from your Google Cloud project.
spec:
 identityProviders:
 - name: Google                 # This is the name that will appear on the login page
   mappingMethod: claim
   type: OpenID
   openID:
     clientID: <your-google-client-id>
     clientSecret:
       name: google-secret      # The name of the secret you created in Step 1
     extraScopes:
     - email
     - profile
     issuer: https://accounts.google.com
     claims:
       preferredUsername:
       - email
       name:
       - name
       email:
       - email
Save and close the editor. Then wait until the authentication operator finish reconciling.

Step 3: Get the redirect_uri and Update Google Cloud

This is a crucial step. OpenShift generates a unique callback URL that Google needs to know about for security.

Open your OpenShift cluster's web console in a browser. You should now see the "Google" login option.

Click the Google login button. You will likely be redirected to a Google error page saying something like "Error 400: redirect_uri_mismatch". This is expected!

Copy the entire URL from your browser's address bar. Find the redirect_uri parameter within that URL. It will look something like this:
https://oauth-openshift.apps../oauth2callback/Google

Go to your project in the Google Cloud Console.

Navigate to your OAuth 2.0 Client ID.

Under the "Authorized redirect URIs" section, click "ADD URI" and paste the full redirect_uri you copied.

Click Save.

Login with your google account again and you will see it works!

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.

Leo6Leo · 2025-09-22T17:53:20Z

/jira refresh
/label tide/merge-method-squash

openshift-ci-robot · 2025-09-22T17:53:28Z

@Leo6Leo: This pull request references Jira Issue OCPBUGS-56892, 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 @yanpzhan

Details

In response to this:

/jira refresh
/label tide/merge-method-squash

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.

…th fallbacks and add corresponding unit tests

openshift-ci-robot · 2025-09-22T18:14:36Z

@Leo6Leo: This pull request references Jira Issue OCPBUGS-56892, 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 @yanpzhan

Details

In response to this:

Closes #13744

Description

After logging in with Google OAuth OIDC, the Console can only show username instead of full name as the display name on the top right corner in the console.

Step to test out the changes

Have a cluster that configure the Google OIDC login. If you don't have one, you can follow the instructions I wrote in the Appendix which locates at the bottom of this PR description.

Choose Google-OpenID-Connect as your login option and login with your google account

After your success login, you will see on the right top corner is displaying your full name, instead of your email address.

Special Note

Thanks to @logonoff for the discussion on what would be the better way to resolve this issue.

Appendix: How to configure Google OAuth on your cluster for testing purpose

Prerequisites

Before you begin, you'll need:

Administrator access to your OpenShift cluster using the oc and kubectl CLI.

A Google Cloud project with an OAuth 2.0 Client ID and Client Secret created. If you need to create one, follow Google's official documentation.

Step 1: Create the Google Client Secret in OpenShift

First, create a k8s secret in the openshift-config namespace to securely store your Google OAuth client secret. This prevents storing sensitive values directly in the main cluster configuration.

Replace <your-google-client-secret> with the actual client secret from your Google Cloud project.
oc create secret generic google-secret \
 --from-literal=clientSecret=<your-google-client-secret> \
 -n openshift-config
Step 2: Configure the Cluster OAuth Identity Provider

Next, edit the cluster-wide OAuth configuration to add Google as an identity provider.
oc edit oauth cluster
Replace with the Client ID from your Google Cloud project.
spec:
 identityProviders:
 - name: Google                 # This is the name that will appear on the login page
   mappingMethod: claim
   type: OpenID
   openID:
     clientID: <your-google-client-id>
     clientSecret:
       name: google-secret      # The name of the secret you created in Step 1
     extraScopes:
     - email
     - profile
     issuer: https://accounts.google.com
     claims:
       preferredUsername:
       - email
       name:
       - name
       email:
       - email
Save and close the editor. Then wait until the authentication operator finish reconciling.

Step 3: Get the redirect_uri and Update Google Cloud

This is a crucial step. OpenShift generates a unique callback URL that Google needs to know about for security.

Open your OpenShift cluster's web console in a browser. You should now see the "Google" login option.

Click the Google login button. You will likely be redirected to a Google error page saying something like "Error 400: redirect_uri_mismatch". This is expected!

Copy the entire URL from your browser's address bar. Find the redirect_uri parameter within that URL. It will look something like this:
https://oauth-openshift.apps../oauth2callback/Google

Go to your project in the Google Cloud Console.

Navigate to your OAuth 2.0 Client ID.

Under the "Authorized redirect URIs" section, click "ADD URI" and paste the full redirect_uri you copied.

Click Save.

Login with your google account again and you will see it works!

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.

Leo6Leo · 2025-09-22T18:21:56Z

/cc @logonoff @jhadvig

logonoff · 2025-09-22T18:23:15Z

frontend/public/components/masthead/masthead-toolbar.tsx

    const userToggle = (
      <span className="co-username" data-test="username">
-        {authEnabledFlag ? username : t('public~Auth disabled')}
+        {authEnabledFlag ? displayName || username || 'User' : t('public~Auth disabled')}


displayName will always return a value so i am not sure if we need the fallback values here

logonoff · 2025-09-22T18:23:24Z

frontend/packages/console-shared/src/hooks/useUser.ts

+      return currentUsername.trim();
+    }
+    // Final fallback for edge cases
+    return 'Unknown User';


should either add i18n or return null (to allow for fallback values to fallback)

frontend/packages/console-dynamic-plugin-sdk/src/app/redux-types.ts

frontend/packages/console-dynamic-plugin-sdk/src/app/core/reducers/coreSelectors.ts

Co-authored-by: logonoff <git@logonoff.co>

Leo6Leo · 2025-10-30T18:13:26Z

/retest-required
Permission Denied issue, flaky

Leo6Leo · 2025-11-03T15:11:04Z

/retest

Leo6Leo · 2025-11-04T18:32:44Z

/retest-required

jhadvig · 2025-11-05T11:53:43Z

/retest

Leo6Leo · 2025-11-06T14:16:53Z

/retest-required

Leo6Leo · 2025-11-10T16:24:58Z

/assign @yapei @yanpzhan
All the tests are now passing, thanks for re-verifying it

yanpzhan · 2025-11-11T08:27:38Z

@Leo6Leo there is conflict for the pr code, cluster-bot could not launch cluster with the pr, could you please rebase the code?

…ail-shown-insteadof-name

logonoff · 2025-11-12T19:12:07Z

/lgtm

openshift-ci · 2025-11-12T19:12:26Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Leo6Leo, logonoff

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~frontend/OWNERS~~ [logonoff]

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

Leo6Leo · 2025-11-13T14:26:34Z

@yanpzhan The PR has been successfully rebased, please let me know if any further action is needed, thanks!

yanpzhan · 2025-11-14T08:31:58Z

Checked on cluster launched against the pr, the full name is shown as expected.
/verified by @yanpzhan

openshift-ci-robot · 2025-11-14T08:32:11Z

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

Details

In response to this:

Checked on cluster launched against the pr, the full name is shown as expected.
/verified by @yanpzhan

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 · 2025-11-14T12:09:38Z

@Leo6Leo: 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/okd-scos-e2e-aws-ovn	`cbecd50`	link	false	`/test okd-scos-e2e-aws-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.

openshift-ci-robot · 2025-11-14T12:25:07Z

/retest-required

Remaining retests: 0 against base HEAD d673d10 and 2 for PR HEAD cbecd50 in total

openshift-ci-robot · 2025-11-15T05:13:37Z

@Leo6Leo: Jira Issue OCPBUGS-56892 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

Details

In response to this:

Closes #13744

Description

After logging in with Google OAuth OIDC, the Console can only show username instead of full name as the display name on the top right corner in the console.

Step to test out the changes

Have a cluster that configure the Google OIDC login. If you don't have one, you can follow the instructions I wrote in the Appendix which locates at the bottom of this PR description.

Choose Google-OpenID-Connect as your login option and login with your google account

After your success login, you will see on the right top corner is displaying your full name, instead of your email address.

Special Note

Thanks to @logonoff for the discussion on what would be the better way to resolve this issue.

Appendix: How to configure Google OAuth on your cluster for testing purpose

Prerequisites

Before you begin, you'll need:

Administrator access to your OpenShift cluster using the oc and kubectl CLI.

A Google Cloud project with an OAuth 2.0 Client ID and Client Secret created. If you need to create one, follow Google's official documentation.

Step 1: Create the Google Client Secret in OpenShift

First, create a k8s secret in the openshift-config namespace to securely store your Google OAuth client secret. This prevents storing sensitive values directly in the main cluster configuration.

Replace <your-google-client-secret> with the actual client secret from your Google Cloud project.
oc create secret generic google-secret \
 --from-literal=clientSecret=<your-google-client-secret> \
 -n openshift-config
Step 2: Configure the Cluster OAuth Identity Provider

Next, edit the cluster-wide OAuth configuration to add Google as an identity provider.
oc edit oauth cluster
Replace with the Client ID from your Google Cloud project.
spec:
 identityProviders:
 - name: Google                 # This is the name that will appear on the login page
   mappingMethod: claim
   type: OpenID
   openID:
     clientID: <your-google-client-id>
     clientSecret:
       name: google-secret      # The name of the secret you created in Step 1
     extraScopes:
     - email
     - profile
     issuer: https://accounts.google.com
     claims:
       preferredUsername:
       - email
       name:
       - name
       email:
       - email
Save and close the editor. Then wait until the authentication operator finish reconciling.

Step 3: Get the redirect_uri and Update Google Cloud

This is a crucial step. OpenShift generates a unique callback URL that Google needs to know about for security.

Open your OpenShift cluster's web console in a browser. You should now see the "Google" login option.

Click the Google login button. You will likely be redirected to a Google error page saying something like "Error 400: redirect_uri_mismatch". This is expected!

Copy the entire URL from your browser's address bar. Find the redirect_uri parameter within that URL. It will look something like this:
https://oauth-openshift.apps../oauth2callback/Google

Go to your project in the Google Cloud Console.

Navigate to your OAuth 2.0 Client ID.

Under the "Authorized redirect URIs" section, click "ADD URI" and paste the full redirect_uri you copied.

Click Save.

Login with your google account again and you will see it works!

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.

Leo6Leo · 2025-11-17T14:56:53Z

/cherry-pick release-4.20

openshift-cherrypick-robot · 2025-11-17T14:57:35Z

@Leo6Leo: #15522 failed to apply on top of branch "release-4.20":

Applying: fix: Update CoreState type to include userResource for k8s API integration
Applying: feat: Add userResource management to core actions and reducer
Applying: feat: Introduce useUser hook for centralized user data management
Applying: refactor: Replace direct user data fetching with centralized useUser hook in telemetry and masthead components
Using index info to reconstruct a base tree...
A	frontend/public/components/masthead/masthead-toolbar.tsx
Falling back to patching base and 3-way merge...
Auto-merging frontend/public/components/masthead-toolbar.jsx
CONFLICT (content): Merge conflict in frontend/public/components/masthead-toolbar.jsx
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0004 refactor: Replace direct user data fetching with centralized useUser hook in telemetry and masthead components

Details

In response to this:

/cherry-pick release-4.20

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.

…s the display name (openshift#15522) * fix: Update CoreState type to include userResource for k8s API integration * feat: Add userResource management to core actions and reducer * feat: Introduce useUser hook for centralized user data management * refactor: Replace direct user data fetching with centralized useUser hook in telemetry and masthead components * test: auto generated the unit tests for useUser hook to validate user data retrieval and dispatch behavior * feat: Enhance useUser hook to provide robust display name handling with fallbacks and add corresponding unit tests * fix: apply the review feedback * Apply suggestions from code review Co-authored-by: logonoff <git@logonoff.co> * feat: run i18n * feat: Add UserKind type import * Apply suggestions from code review Co-authored-by: logonoff <git@logonoff.co> * Update frontend/public/locales/en/public.json Co-authored-by: logonoff <git@logonoff.co> * Update frontend/packages/console-dynamic-plugin-sdk/src/app/core/actions/core.ts Co-authored-by: logonoff <git@logonoff.co> * feat: Import UserKind type in core actions * refactor: Update GetUserResource type to use UserKind for improved type safety * test: Update useUser.spec.ts to mock setUserResource and correct displayName expectation * test: fixing the failing CI issue --------- Co-authored-by: logonoff <git@logonoff.co>

…s the display name (openshift#15522) Cherry-picked from efd72db with conflict resolution adapted for 4.19 branch.

Leo6Leo added 5 commits September 22, 2025 12:17

fix: Update CoreState type to include userResource for k8s API integr…

0d84540

…ation

feat: Add userResource management to core actions and reducer

2c59766

feat: Introduce useUser hook for centralized user data management

e81d4fc

refactor: Replace direct user data fetching with centralized useUser …

308f1d7

…hook in telemetry and masthead components

test: auto generated the unit tests for useUser hook to validate user…

824bb98

… data retrieval and dispatch behavior

openshift-ci bot requested review from TheRealJon and cajieh September 22, 2025 17:51

openshift-ci bot added component/core Related to console core functionality component/sdk Related to console-plugin-sdk component/shared Related to console-shared labels Sep 22, 2025

openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Sep 22, 2025

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 22, 2025

openshift-ci bot requested a review from yanpzhan September 22, 2025 17:53

feat: Enhance useUser hook to provide robust display name handling wi…

2cbbed8

…th fallbacks and add corresponding unit tests

openshift-ci bot requested review from jhadvig and logonoff September 22, 2025 18:21

logonoff reviewed Sep 22, 2025

View reviewed changes

frontend/packages/console-dynamic-plugin-sdk/src/app/redux-types.ts Outdated Show resolved Hide resolved

frontend/packages/console-dynamic-plugin-sdk/src/app/core/reducers/coreSelectors.ts Outdated Show resolved Hide resolved

Leo6Leo and others added 2 commits September 22, 2025 14:34

fix: apply the review feedback

ccb1777

Apply suggestions from code review

aedb5b8

Co-authored-by: logonoff <git@logonoff.co>

openshift-ci bot assigned yanpzhan Nov 10, 2025

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 11, 2025

Merge remote-tracking branch 'upstream' into leo/ocpbugs/56892/userem…

cbecd50

…ail-shown-insteadof-name

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 12, 2025

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 12, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 12, 2025

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 14, 2025

openshift-merge-bot bot merged commit efd72db into openshift:main Nov 15, 2025
7 of 8 checks passed

Leo6Leo mentioned this pull request Nov 19, 2025

[release-4.20] OCPBUGS-65793: OpenShift Console can only show user name instead of full name as the display name #15743

Merged

krishagarwal278 mentioned this pull request Dec 3, 2025

OCPBUGS-66105: Lack of kebab list on projects list page for normal user #15801

Merged

Leo6Leo added a commit to Leo6Leo/console that referenced this pull request Jan 5, 2026

OCPBUGS-56892: Console can only show user name instead of full name a…

90071ed

…s the display name (openshift#15522) Cherry-picked from efd72db with conflict resolution adapted for 4.19 branch.

Leo6Leo mentioned this pull request Jan 5, 2026

[release-4.19] OCPBUGS-70335: OpenShift Console can only show user name instead of full name as the display name #15888

Merged

OCPBUGS-56892: Console can only show user name instead of full name as the display name #15522

OCPBUGS-56892: Console can only show user name instead of full name as the display name #15522

Uh oh!

Conversation

Leo6Leo commented Sep 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Step to test out the changes

Special Note

Appendix: How to configure Google OAuth on your cluster for testing purpose

Prerequisites

Step 1: Create the Google Client Secret in OpenShift

Step 2: Configure the Cluster OAuth Identity Provider

Step 3: Get the redirect_uri and Update Google Cloud

Uh oh!

openshift-ci-robot commented Sep 22, 2025

Description

Step to test out the changes

Special Note

Appendix: How to configure Google OAuth on your cluster for testing purpose

Prerequisites

Step 1: Create the Google Client Secret in OpenShift

Step 2: Configure the Cluster OAuth Identity Provider

Step 3: Get the redirect_uri and Update Google Cloud

Uh oh!

Leo6Leo commented Sep 22, 2025

Uh oh!

openshift-ci-robot commented Sep 22, 2025

Uh oh!

openshift-ci-robot commented Sep 22, 2025

Description

Step to test out the changes

Special Note

Appendix: How to configure Google OAuth on your cluster for testing purpose

Prerequisites

Step 1: Create the Google Client Secret in OpenShift

Step 2: Configure the Cluster OAuth Identity Provider

Step 3: Get the redirect_uri and Update Google Cloud

Uh oh!

Leo6Leo commented Sep 22, 2025

Uh oh!

logonoff Sep 22, 2025

Choose a reason for hiding this comment

Uh oh!

logonoff Sep 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Leo6Leo commented Oct 30, 2025

Uh oh!

Leo6Leo commented Nov 3, 2025

Uh oh!

Leo6Leo commented Nov 4, 2025

Uh oh!

jhadvig commented Nov 5, 2025

Uh oh!

Leo6Leo commented Nov 6, 2025

Uh oh!

Leo6Leo commented Nov 10, 2025

Uh oh!

yanpzhan commented Nov 11, 2025

Uh oh!

logonoff commented Nov 12, 2025

Uh oh!

openshift-ci bot commented Nov 12, 2025

Uh oh!

Leo6Leo commented Nov 13, 2025

Uh oh!

yanpzhan commented Nov 14, 2025

Uh oh!

openshift-ci-robot commented Nov 14, 2025

Uh oh!

openshift-ci bot commented Nov 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Nov 14, 2025

Uh oh!

Uh oh!

Leo6Leo commented Sep 22, 2025 •

edited

Loading

logonoff Sep 22, 2025 •

edited

Loading

openshift-ci bot commented Nov 14, 2025 •

edited

Loading