Bug 2079611

Summary:	Edit appset placement in UI with a different existing placement causes the current associated placement being deleted
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:

Description Thuy Nguyen 2022-04-27 21:27:42 UTC

Description of problem: Edit appset placement in UI with an existing placement causes the current associated placement being deleted 

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 created and deployed OK
3. Edit the appset, go to Placement page, select 'Existing placement', select an existing placement from the list, submit the changes

Actual results:
The placement created in step 1 will be delete upon submitting editing requests

Expected results:


Additional info:

Comment 1 bot-tracker-sync 2022-05-04 20:06:12 UTC

G2Bsync 1117668981 comment 
 thuyn-581 Wed, 04 May 2022 18:29:05 UTC 
 G2BSync -

Retest failed on ACM 2.5.0-DOWNSTREAM-2022-05-02-16-00-32.

Steps to reproduce:
1. Create a new appset, go to 'Placement' page, select existing placement, submit
2. Apps created and deployed successfully
3. Edit the appset in step 1, go to Placement, select new cluster set, submit
4. Error seen

<img width="1438" alt="Screen Shot 2022-05-04 at 2 27 05 PM" src="https://user-images.githubusercontent.com/60235374/166801561-3eca2a34-94e3-4e08-ab04-3f8eb2f7e2f1.png">

Comment 2 bot-tracker-sync 2022-05-10 15:15:26 UTC

G2Bsync 1122418168 comment 
 KevinFCormier Tue, 10 May 2022 13:44:46 UTC 
 G2Bsync Re-fixed for May 10th

Comment 3 bot-tracker-sync 2022-05-12 16:09:31 UTC

G2Bsync 1125154297 comment 
 thuyn-581 Thu, 12 May 2022 15:46:02 UTC 
 G2BSync -
Validated on ACM 2.5.0-DOWNSTREAM-2022-05-10-21-30-52.

Comment 7 errata-xmlrpc 2022-06-09 02:11:44 UTC

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