-
Epic
-
Resolution: Unresolved
-
Critical
-
ACM 2.11.0
Epic Goal
...
In my env I have clusters feng-mc1 and feng-mc2. We limit cluster to 1
The application was initially deployed to feng-mc2 which I then hibernated and caused the application to be deployed to feng-mc1. In the PlacementDecision we can see that feng-mc1 is now selected but the UI is still displaying both clusters because the MulticlusterApplicationSetReport still shows both clusters.
Why is this important?
...
we need to display the correct numbers of clusters else customer would be irritated
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.