Bug 2079615
| Summary: | Edit appset placement in UI with a new placement throws error upon submitting | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Thuy Nguyen <thnguyen> | ||||
| Component: | Console | Assignee: | James Talton <jtalton> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Xiang Yin <xiyin> | ||||
| Severity: | medium | Docs Contact: | Christopher Dawson <cdawson> | ||||
| Priority: | unspecified | ||||||
| Version: | rhacm-2.5 | CC: | dho, dhuynh, huichen | ||||
| Target Milestone: | --- | Flags: | bot-tracker-sync:
rhacm-2.5+
|
||||
| Target Release: | rhacm-2.5 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-06-09 02:11:44 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
G2Bsync 1117671132 comment thuyn-581 Wed, 04 May 2022 18:31:24 UTC G2BSync - Validated on ACM 2.5.0-DOWNSTREAM-2022-05-02-16-00-32. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:4956 |
Created attachment 1875506 [details] Edit app set UI Description of problem: Edit appset placement in UI with a new placement throws error upon submitting Version-Release number of selected component (if applicable): ACM 2.5.0-DOWNSTREAM-2022-04-26-23-16-11 How reproducible: Steps to Reproduce: 1. Create application set with a new placement by label selector of matching name 2. Associated app/placement created and deployed OK 3. Edit the appset, go to Placement page, select 'New placement', select a clusterset from dropdown list 4. Submit Actual results: Erorr 'placements.cluster.open-cluster-management.io "appset-git-gb-placement" already exists' is fired out Expected results: Additional info: