Bug 1948508 - incorrect option base64 -D when generating the command to import a cluster
Summary: incorrect option base64 -D when generating the command to import a cluster
Keywords:
Status: CLOSED DUPLICATE of bug 1936642
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.2
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: rhacm-2.2.2
Assignee: James Talton
QA Contact: Hui Chen
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-12 10:27 UTC by Felix Dewaleyne
Modified: 2024-06-14 01:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-15 02:14:15 UTC
Target Upstream Version:
Embargoed:
ming: rhacm-2.2.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 11396 0 None None None 2021-04-12 18:04:47 UTC

Description Felix Dewaleyne 2021-04-12 10:27:04 UTC
Description of problem:
incorrect option base64 -D when generating the command to import a cluster
the correct option is -d ; this could throw errors.

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

How reproducible:
customer environment

Steps to Reproduce:
1. Login in the the RAHCM Console
2. Menu > Automate Infrastructure > Clusters
3. Add a cluster > Import an existing cluster
4. Fill any value for the cluster name
5. Click on "Save import and generate code"
6. Click on "Copy command"
7. Paste the command 

Actual results:
the command ends with "| base64 -D" which can raise an error.

Expected results:
the command ends with "| base64 -d" 

Additional info:
openshift 4.6.22 was used on the customer environment.

Comment 1 Mike Ng 2021-04-13 16:40:48 UTC
G2Bsync 818335090 comment 
 chrisahl Tue, 13 Apr 2021 00:32:07 UTC 
 G2Bsync
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1936642 (and maybe others) and is fixed in 2.2.2

Comment 2 Yuanyuan He 2021-11-15 02:14:15 UTC

*** This bug has been marked as a duplicate of bug 1936642 ***

Comment 3 Derek Ho 2021-11-16 18:24:56 UTC
Update QA contact for CLC


Note You need to log in before you can comment on or make changes to this bug.