Bug 1934184

Summary: When generating the import cluster string, it can include unescaped characters
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Felix Dewaleyne <fdewaley>
Component: Cluster LifecycleAssignee: cahl
Status: CLOSED ERRATA QA Contact: Hui Chen <huichen>
Severity: high Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.1CC: cahl, fdewaley
Target Milestone: ---Flags: huichen: qe_test_coverage+
ming: rhacm-2.1.z+
Target Release: rhacm-2.1.6   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-26 15:56:11 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:

Description Felix Dewaleyne 2021-03-02 16:37:29 UTC 
Description of problem:
When generating an import cluster command, the generated command can include unescaped characters in the echo structure

Version-Release number of selected component (if applicable):
2.1

How reproducible:
customer environment

Steps to Reproduce:
1. click on clusters
2. click on import cluster
3. copy text

Actual results:
the string can include unescaped characters such as == that can be interpreted by the terminal incorrectly

Expected results:
the string includes quotes to escape the characters so that they aren't interpreted incorrectly

Additional info:
a sample provided included == at the end which, unescaped, caused errors.
escaping the string fixes the issue.
Comment 2 Felix Dewaleyne 2021-03-16 09:54:04 UTC 
version is 2.1.4 more precisely
Comment 9 errata-xmlrpc 2021-04-26 15:56:11 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.1.6 security and bug fix updates), 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-2021:1369