Bug 2055900

Summary:	If MCH is installed on existing MCE and both are in multicluster-engine namespace , uninstalling MCH terminates multicluster-engine namespace
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	txue
Component:	Installer	Assignee:	Jakob <jagray>
Status:	CLOSED ERRATA	QA Contact:	txue
Severity:	medium	Docs Contact:	Christopher Dawson <cdawson>
Priority:	unspecified
Version:	rhacm-2.5	CC:	alisauxbpn53, jwakely, maxburns090, ri.chardfoxmx63577
Target Milestone:	---	Flags:	bot-tracker-sync: rhacm-2.5+
Target Release:	rhacm-2.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ACM 2.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-09 02:11:10 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 txue 2022-02-17 21:42:47 UTC

Description of the problem:
If MCH is installed on existing MCE,  and both are in multicluster-engine namespace , uninstalling MCH terminates multicluster-engine namespace.
This only happens when the name space is multicluster-engine, which is the default name space for MCE. If both are installed in other namesapce like, ocm, uninstall MCH works well, doesn't hurt existing MCE.
Release version:
ACM 2.5
Operator snapshot version:
Final sprint 2 build 2.5.0-DOWNSTREAM-2022-02-16-19-52-49
OCP version:

Browser Info:

Steps to reproduce:
1.Install MCE in the default name space: multicluster-engine
2.Install ACM in the same namespace multicluster-engine
3.After MCH is installed, try delete MCH.

Actual results:
all the pods in multicluster-engine are gone. multicluster-engine is terminating.
Expected results:
multicluster-engine name space remains and MCE pods should remain running.
Additional info:

Comment 5 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

Comment 7 max burns 2023-06-07 08:53:39 UTC Comment hidden (spam)

Based on the information provided, it seems that there is an issue when uninstalling the MultiClusterHub (MCH) component of ACM (Advanced Cluster Management) when both MCH and MCE (MultiCluster Engine) are installed in the multicluster-engine namespace. The uninstallation of MCH results in the termination of the entire multicluster-engine namespace, including the MCE pods.

This behavior might be specific to the default namespace used for MCE, as you mentioned that if both MCH and MCE are installed in a different namespace like ocm, the uninstallation of MCH does not impact the existing MCE pods.

To investigate and resolve this issue, you can take the following steps:

Check the logs and events related to the uninstallation process of MCH. Look for any error messages or warnings that might provide insight into why the multicluster-engine namespace is being terminated.

Verify the dependencies and configurations between MCH and MCE. Ensure that the uninstallation of MCH does not have any unintended effects on the multicluster-engine namespace or the MCE pods.

Consult the documentation or reach out to the support channels specific to ACM and MCE for further assistance. They can provide guidance and help troubleshoot the issue based on their knowledge of the ACM and MCE components.

It's worth noting that debugging and resolving this issue might require access to the specific environment, configurations, and logs. Therefore, it would be beneficial to involve the support teams or consult the official documentation for the most accurate guidance and troubleshooting steps.  https://www.ballsportspro.com/can-you-hit-a-pickleball-with-your-hand-read-before-you-play/

Comment 8 Karmin 2023-06-30 04:14:58 UTC Comment hidden (spam)

It appears that you are facing an issue when uninstalling the Multicluster Hub (MCH) in a specific scenario where both MCH and Multicluster Engine (MCE) are installed in the "multicluster-engine" namespace. Uninstalling MCH in this case terminates the "multicluster-engine" namespace, resulting in the deletion of all pods within that namespace.

However, if both MCH and MCE are installed in a different namespace, such as "ocm", uninstalling MCH works correctly without affecting the existing MCE pods.

To resolve this issue, you may consider the following steps:

Backup any important data or configurations related to the "multicluster-engine" namespace.
Remove the existing MCH installation.
Manually recreate the "multicluster-engine" namespace if it was terminated during the uninstallation process.
Deploy MCE in the "multicluster-engine" namespace.
Verify that the MCE pods are running correctly.
It's important to note that troubleshooting and resolving specific issues related to the Multicluster Hub (MCH) and Multicluster Engine (MCE) in the context of ACM 2.5 and the provided Operator snapshot version may require deeper analysis and assistance from the product's support team or community forums. https://www.yourtexasbenefits.bid/