Description of problem: ACM Y-upgrade from 2.14.0 to 2.15 failed, the jenkins job https://jenkins-csb-rhacm-tests.dno.corp.redhat.com/job/acm/job/acm-upgrade/399/console reports error:

FAILED - RETRYING: [localhost]: Wait for csv 2.10.0 in namespace multicluster-engine to be Succeeded (2 retries left).
FAILED - RETRYING: [localhost]: Wait for csv 2.10.0 in namespace multicluster-engine to be Succeeded (1 retries left).
fatal: [localhost]: FAILED! => {"attempts": 30, "changed": true, "cmd": "oc -n multicluster-engine get csv -oname |\\\ngrep 2.10.0 |\\\nxargs oc -n multicluster-engine get -ojson | jq -r '.status.phase'\n", "delta": "0:00:00.765045", "end": "2025-10-15 06:19:48.060987", "msg": "", "rc": 0, "start": "2025-10-15 06:19:47.295942", "stderr": "", "stderr_lines": [], "stdout": "Pending", "stdout_lines": ["Pending"]}

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

ACM - 2.15.0-DOWNSTREAM-2025-10-14-15-17-47
MCE - 2.10.0-DOWNSTREAM-2025-10-14-19-11-47

How reproducible:

Steps to Reproduce:

1. Deploy ACM 2.14.0
2. upgrade to ACM 2.15 by the jenkins job https://jenkins-csb-rhacm-tests.dno.corp.redhat.com/job/acm/job/acm-upgrade/399/console
3. ...

Actual results:

Expected results:

Additional info:

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