Bug 2078164 - Failed to edit a policy without placement
Summary: Failed to edit a policy without placement
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.5
Assignee: James Talton
QA Contact: Xiang Yin
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-24 05:16 UTC by yahliu
Modified: 2022-06-09 02:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-09 02:11:35 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.5+

Attachments (Terms of Use)
failed-0504 (682.12 KB, image/png)
2022-05-07 03:09 UTC, yahliu 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 21914 0 None None None 2022-04-24 08:58:43 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:11:46 UTC

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
Note You need to log in before you can comment on or make changes to this bug.