Bug 2075724

Summary: Changing existing placement rules does not change YAML file
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Almen Ng <almng>
Component: ConsoleAssignee: Kevin Cormier <kcormier>
Status: CLOSED ERRATA QA Contact: Xiang Yin <xiyin>
Severity: high Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.4.zCC: crizzo, dho, dhuynh, ecai, huichen, rbrunopi
Target Milestone: ---Keywords: Regression
Target Release: rhacm-2.4.5Flags: almng: rhacm-2.4.z+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2079013 (view as bug list) Environment:
Last Closed: 2022-06-27 17:04:02 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:

Comment 10 errata-xmlrpc 2022-06-27 17:04:02 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 (Moderate: Red Hat Advanced Cluster Management 2.4.5 security updates 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:5201

Comment 11 Red Hat Bugzilla 2023-09-15 01:53:56 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days