Bug 2079013

Summary: Changing existing placement rules does not change YAML file
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Kevin Cormier <kcormier>
Component: ConsoleAssignee: magchen@redthat.com <magchen>
Status: CLOSED ERRATA QA Contact: Almen Ng <almng>
Severity: high Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.4.zCC: almng, cdawson, crizzo, dho, dhuynh, ecai, fxiang, huichen, xiyin
Target Milestone: ---Keywords: Regression
Target Release: rhacm-2.5Flags: kcormier: 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: 2075724 Environment:
Last Closed: 2022-06-09 02:11:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 Feng Xiang 2022-05-04 19:58:26 UTC
Just want to add this is also blocking the QE automation work(Git_Application_Test_Suite).

Comment 2 bot-tracker-sync 2022-05-05 14:43:41 UTC
G2Bsync 1118532029 comment 
 KevinFCormier Thu, 05 May 2022 13:12:15 UTC 
 G2Bsync Fix has been merged. Please verify with builds from May 5th onward.

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