-
Story
-
Resolution: Unresolved
-
Major
-
MCE 2.8.0
Value Statement
Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")
Definition of Done for Engineering Story Owner (Checklist)
- Hive upgrade sample issue: https://github.com/stolostron/backlog/issues/26722(MCE 2.2 hive upgrade)
Mce-2.4 upgrade hive checklist:
-
- Hive team cuts mce-2.4 branch
- CLC team test new hive for each cloud providers
- will collab with QE. Patch an env with the new hive branch and run the e2e through QE's jenkins pipeline for validation. - Once https://issues.redhat.com/browse/ACM-3912 and https://issues.redhat.com/browse/ACM-3914 are complete, CLC team upgrade hive in[ https://github.com/stolostron/cluster-curator-controller|https://github.com/stolostron/cluster-curator-controller] and https://github.com/stolostron/clusterclaims-controller
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. <–not applicable - [ ] 100% automated unit/function test coverage for new or changed APIs. <–not applicable
Secure Design
- [ ] Security has been assessed and incorporated into your threat model. <–not applicable
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template]( <–not applicable
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [x] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated. <–not applicable
- clones
-
ACM-15603 [Train-22] MCE 2.8 hive upgrade
- Review