Description of problem:

Within the past few weeks, we've had some failures in our Discovery Cypress automation. We analyzed them and were unable to resolve most of them. After speaking to the Console team, we believe there might be a potential defect here. This is all we have gotten to run so far so there might be other issues in other screens.

• When creating a Discovery credential, the "Authentication Method" drop down behaves strangely.
• If you select API Token, the field populates as false,API token
• If you select Service account, the field populates as service-account (minor but a difference).
• In our Cypress automation, we had to update cy.get("#ocmAuthMethod") to cy.get("#ocmAuthMethod li")

• When setting up Discovery Settings, the drop down for "Red Hat OpenShift version" seems to have changed behind the scenes and we can't figure it out.
• When selecting all of them, our automation works.
• When selecting one of them, it fails and we think it might be related to this line: cy.get(".pf-v5-c-select__toggle-text").invoke("text").as("versions");

• When trying to delete Discovery credentials, it fails trying to find the Delete button, which seems easy enough so we can't figure out what is wrong: cy.contains("button","Delete").click();

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

ACM 2.14

How reproducible:

Always

Steps to Reproduce:

1. Run installer Discovery Cypress automation
2. Note failures described above.

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 6/30/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