-
Spike
-
Resolution: Done
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
-
-
-
Installer Sprint 2025-67
-
None
Value Statement
When a customer installs ACM to manage their standalone MCE instance, they can still update the MCE operator version through OLM. This can lead to issues, as ACM relies on a specific MCE version. To avoid this, it’s recommended to first update the ACM operator, which will allow MCE to update automatically. By updating MCH, we can track the MCE status and identify if ACM is partially upgraded, offering a clearer status for customers to understand the current state of the cluster.
Definition of Done for Engineering Story Owner (Checklist)
- [] MCH status reflects if MCE X.Y version is greater than the required channel.
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- relates to
-
ACM-23826 MCH: As an Installer developer, I want the MCH CR to indicate whether the MCE X.Y version exceeds the required MCE version
-
- Review
-