-
Story
-
Resolution: Done
-
Major
-
MCE 2.3.0
-
5
-
False
-
None
-
False
-
-
-
-
Console Sprint 2023-05
-
No
Value Statement
Hive behaviour is changing such that a ClusterPool will not be fully deleted until all clusters claimed from the pool are also deleted. See https://issues.redhat.com/browse/HIVE-1557
The MCE console ClusterPool behaviour should be updated accordingly.
Definition of Done for Engineering Story Owner (Checklist)
- All actions on a ClusterPool that has a deletionTimestamp should be disabled. This includes Delete, scale, claim cluster.
- There should be some indication that the ClusterPool is being deleted and will persist until all clusters claimed from the pool are deleted.
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [x] Unit/function tests have been automated and incorporated into the
build. - [x] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ na] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [x] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
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
- [na] The must-gather script has been updated.
- causes
-
ACM-5066 Cluster pool destruction status is inconsistent with other areas
- Closed
- depends on
-
ACM-3391 Updating the Version of Hive in each MCE releases
- Closed
-
ACM-3912 Update hive commit based on mce-2.3 hive branch
- Closed
- is related to
-
HIVE-1557 ClusterPool deletion should wait until all unclaimed clusters are destroyed
- Closed
There are no Sub-Tasks for this issue.