Bug 2107359 - cluster uninstall log points to incorrect container name
Summary: cluster uninstall log points to incorrect container name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.6
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.5.2
Assignee: Kevin Cormier
QA Contact: dhuynh
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-14 19:28 UTC by Thuy Nguyen
Modified: 2022-09-13 20:06 UTC (History)
3 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 24302 0 None None None 2022-07-14 21:27:31 UTC
Red Hat Product Errata RHSA-2022:6507 0 None None None 2022-09-13 20:06:41 UTC

Description Thuy Nguyen 2022-07-14 19:28:33 UTC 
Description of problem: cluster uninstall log points to incorrect container name


Version-Release number of selected component (if applicable):
ACM 2.6.0-DOWNSTREAM-2022-07-13-23-23-00

How reproducible:


Steps to Reproduce:
1. Create cluster in ACM successfully
2. Destroy the cluster created in step 1
3. Click to view uninstall log

Actual results:
the embedded link is at `https://console-openshift-console.apps.ocp4-aws-dr-3.dev09.red-chesterfield.com/k8s/ns/s3-aws-tn/pods/s3-aws-tn-uninstall-sdt4h/logs?container=hive`

Expected results:
The container should be 'deprovision'

Additional info:
Comment 1 bot-tracker-sync 2022-07-26 00:55:15 UTC 
G2Bsync 1194753485 comment 
 thuyn-581 Mon, 25 Jul 2022 23:13:38 UTC 
 G2BSync -
Validated on MCE 2.0.2-DOWNANDBACK-2022-07-25-15-12-51.
Comment 6 errata-xmlrpc 2022-09-13 20:06:28 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 (Critical: Red Hat Advanced Cluster Management 2.5.2 security fixes 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:6507
Note You need to log in before you can comment on or make changes to this bug.