Bug 2054772 - credentialName is not parsed correctly in UI notifications/alerts when creating/updating a discovery config
Summary: credentialName is not parsed correctly in UI notifications/alerts when creati...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Installer
Version: rhacm-2.5
Hardware: x86_64
OS: Unspecified
unspecified
low
Target Milestone: ---
: rhacm-2.5
Assignee: Jakob
QA Contact: txue
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-15 16:52 UTC by Thuy Nguyen
Modified: 2022-06-09 02:11 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
UI notification (398.88 KB, image/png)
2022-02-15 16:52 UTC, Thuy Nguyen 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 19973 0 None None None 2022-02-15 19:54:59 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:11:22 UTC

Description Thuy Nguyen 2022-02-15 16:52:14 UTC 
Created attachment 1861301 [details]
UI notification

Description of the problem: credentialName is not parsed correctly in UI notifications/alerts when creating/updating a discovery config

Release version:

Operator snapshot version: 
- ACM 2.5.0-DOWNSTREAM-2022-02-14-13-53-12
- MCE 2.0.0-DOWNANDBACK-2022-02-14-21-30-26

OCP version:

Browser Info:

Steps to reproduce:
1. Add RHOCM credential
2. Configure/update discovery config using the credential created in step 1


Actual results:
UI notification reads '{{credentialName}} discovery settings was created/updated successfully'


Expected results:
The credentialName should show the actual name

Additional info:
Comment 1 Thuy Nguyen 2022-02-24 18:26:28 UTC 
Validated on ACM 2.5.0-DOWNSTREAM-2022-02-21-19-58-55
Comment 4 errata-xmlrpc 2022-06-09 02:11:10 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.