Bug 2078164

Summary: Failed to edit a policy without placement
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: yahliu
Component: ConsoleAssignee: James Talton <jtalton>
Status: CLOSED ERRATA QA Contact: Xiang Yin <xiyin>
Severity: medium Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.5CC: dho, dhuynh, huichen
Target Milestone: ---Flags: bot-tracker-sync: rhacm-2.5+
Target Release: rhacm-2.5   
Hardware: Unspecified   
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:35 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:
Description Flags
failed-0504 none

Comment 1 yahliu 2022-05-05 02:32:47 UTC 
Failed on 2.5.0-DOWNSTREAM-2022-05-03-02-21-09

Retest steps: 
1. Create a policy by selecting no placement
2. Edit this policy, select the new placement or existing placement
3. Report new error message "Operation cannot be fulfilled on policies.policy.open-cluster-management.io "grc-1": the object has been modified; please apply your changes to the latest version and try again" when click submit.
Comment 2 yahliu 2022-05-07 03:09:41 UTC 
Created attachment 1877705 [details]
failed-0504
Comment 3 yahliu 2022-05-07 03:15:15 UTC 
Failed on 2.5.0-DOWNSTREAM-2022-05-04-22-48-12. 

I created a policy with no placement, after about 10 mins, then edit this policy by selecting new placement, I tried few times, still report the error message "Operation cannot be fulfilled on policies.policy.open-cluster-management.io: the object has been modified; please apply your changes to the latest version and try again". see failed-0504 attachment file.
Comment 4 yahliu 2022-05-11 06:32:14 UTC 
Verified on 2.5.0-DOWNSTREAM-2022-05-10-16-14-44
Comment 8 errata-xmlrpc 2022-06-09 02:11:35 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