Description of problem:

When updating to 2.15, the multicluster-engine installplan was created as manual instead of automatic like in previous updates

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

2.13 to 2.14 to 2.15 upgrade

How reproducible:

customer environment

Steps to Reproduce:

1. set the installplans for ACM to manual
2. upgrade to 2.15

Actual results:

the installplan for MCE is set to manual and the installation needs to be manually accepted to progress the upgrade to 2.15

Expected results:

The MCE upgrade is not created as manual or is automatically accepted as part of the RHACM upgrade

Additional info:

installplans for MCE

omc get installplans -n multicluster-engine
NAME            CSV                           APPROVAL    APPROVED
install-9hsl6   multicluster-engine.v2.9.1    Automatic   true
install-gm5nx   multicluster-engine.v2.8.2    Automatic   true
install-kx7g8   multicluster-engine.v2.8.4    Automatic   true
install-lfkx9   multicluster-engine.v2.10.1   Manual      false
install-vjv88   multicluster-engine.v2.8.3    Automatic   true

Installplans for open-cluster-management

omc get installplans -n open-cluster-management
NAME            CSV                                   APPROVAL   APPROVED
install-czm9s   advanced-cluster-management.v2.13.5   Manual     true
install-fdk6m   advanced-cluster-management.v2.13.4   Manual     true
install-lsxjs   advanced-cluster-management.v2.14.1   Manual     true
install-lvg7m   advanced-cluster-management.v2.13.3   Manual     true
install-wpxjr   advanced-cluster-management.v2.15.1   Manual     true

Only the upgrade to 2.15 caused the multicluster-engine installplan to be set to manual instead of automatic, which was not expected by the customer.

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 2/13/26:

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