Description of problem:

When MCE is awaiting an upgrade to a newer release, the MCH status for the MCE subscription component is incorrect. It mistakenly shows that the version pending installation is already installed, while the current version on the cluster is actually the one that is pending. The order is misleading and should be reversed to accurately reflect that the version awaiting an upgrade is the one that is pending.

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

ACM 2.5.+ (We only need to focus on releases that are still in support)

How reproducible:

Always

Steps to Reproduce:

1. Install ACM and configure MCE to be in manual mode.
2. Ensure that MCE is not at the latest version in the channel.
3. Verify that the MCE subscription status in the MCH CR is reporting incorrectly.

Actual results:

The MCH status for the MCE subscription component incorrectly displays MCE v2.6.6 as installed and MCE v2.6.5 as pending. The order should be reversed to show that MCE v2.6.5 is installed and MCE v2.6.6 is pending.

    multicluster-engine-sub:
      kind: Subscription
      lastTransitionTime: '2025-03-14T16:00:38Z'
      message: 'Upgrade pending. Installed CSV: multicluster-engine.v2.6.6. Pending CSV: multicluster-engine.v2.6.5'
      name: multicluster-engine
      reason: UpgradePending
      status: 'True'
      type: Available

Expected results:

    multicluster-engine-sub:
      kind: Subscription
      lastTransitionTime: '2025-03-14T16:00:38Z'
      message: 'Upgrade pending. Installed CSV: multicluster-engine.v2.6.5. Pending CSV: multicluster-engine.v2.6.6'
      name: multicluster-engine
      reason: UpgradePending
      status: 'True'
      type: Available

Additional info:

OLM Subscription field descriptions:

• InstalledCSV is the CSV currently installed by the Subscription.
• CurrentCSV is the CSV the Subscription is progressing to.