Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-27698

Cannot see Discovery Credential in UI after creation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • ACM 2.16.0
    • Installer
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Installer Train 35 - 1
    • Important
    • None

      Description of problem:

      After creating a Discovery Credential via the UI, it says "You don't have any credentials yet". Via the CLI, I am able to view it.

      $ oc get secret discovery-credential -n discovery-ns
      NAME                   TYPE     DATA   AGE
      discovery-credential   Opaque   2      113m
      

      Version-Release number of selected component (if applicable):

      quay.io:443/acm-d/acm-dev-catalog:2.16.0-DOWNSTREAM-2025-12-15-23-27-00
      quay.io:443/acm-d/mce-dev-catalog:2.11.0-DOWNSTREAM-2025-12-16-05-15-54

      Builds from roughly 1 week before the above builds did not have this problem.

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create a Discovery Credential via the UI (in my case, RHOCM type)

      Actual results:

      The UI page showing all credentials is blank. Trying to make the same one again will hang at the last step.

      Expected results:

      It should be created.

      -------------------------------------------------------------------------------------------------------
      QE Hand Off Template (fill out when moving to Review) 12/18/25:

      Summary of the Work:
      What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
      e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."

      Key Areas to Verify:

      1. What functionality should QE focus on? List what was tested or what is most important to validate.
      2. Ensure the new validation messages appear for required fields
      3. Confirm the workflow still completes as expected after validation fixes
      4. Any edge cases or high-risk areas touched by the change

      Fix or Feature Availability:
      When will this be available in a build?
      Code merged on: YYYY-MM-DD
      Expected downstream build tag (if known): example-build-tag
      (Optional) Related PR(s): Link

              dbennett@redhat.com Disaiah Bennett
              rh-ee-msmigiel Matthew Smigielski
              Matthew Smigielski Matthew Smigielski
              ACM QE Team
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: