Description of problem:

upgrade from a 2.10 that failed to update MCE to a 2.11 was possible

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

2.9 -> 2.10 -> 2.11
mce stuck at 2.4.5

How reproducible:

customer environment

Steps to Reproduce:

1. install 2.9
2. upgrade to 2.10 and run into an issue that will block mce from udating correctly
3. upgrade to 2.11

Actual results:

ACM updated to 2.10 then 2.11, spokes were hit with a lot of addon deployment and update issues due to the mce version mismatch and no metrics were being gathered

Expected results:

it should not be possible to upgrade to 2.11 without MCE having been updated. no install plan for MCE 2.5 was created.

Additional info:

• the customer involved has an automation in place that is automatically applying major upgrades