Bug 2051983

Summary: ACM 2.5 tries to create new MCE instance when install on top of existing MCE 2.0
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: txue
Component: InstallerAssignee: Jakob <jagray>
Status: CLOSED ERRATA QA Contact: txue
Severity: high Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.5CC: juhsu
Target Milestone: ---Flags: bot-tracker-sync: rhacm-2.5+
Target Release: rhacm-2.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-09 02:08:48 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:
Attachments:
Description Flags
screen shot of MCE none

Description txue 2022-02-08 13:26:58 UTC
Created attachment 1859795 [details]
screen shot of MCE

Description of the problem:
ACM 2.5 tries to create new MCE instance when install on top of existing MCE 2.0. 
As shown in the attached screen shot, multiclusterengin-sample was created when MCE itself is installed alone.
Then, after ACM 2.5 is installed. it creates new MCE instance named "multiclusterengin", with labels indicating it's installed by mch, but the status is "Error".
Release version:
ACM 2.5, MCE 2.0
Operator snapshot version:
2.5.0-DOWNSTREAM-2022-02-07-19-47-48
OCP version:
4.9.9
Browser Info:

Steps to reproduce:
1.Install MCE 2.0 downstream build first.
2.After MCE is installed, try to install ACM 2.5 on top of existing MCE
3.

Actual results:
ACM is installed successfully but 2 MCE instances is shown in MCE operator. the one created by ACM shouldn't be there.
Expected results:
only the existing MCE instance should be there.
Additional info:

Comment 1 txue 2022-02-11 03:22:16 UTC
verified with 2.5.0-DOWNSTREAM-2022-02-10-07-31-45

Comment 4 errata-xmlrpc 2022-06-09 02:08:48 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