Bug 2094502 - Creating an MCH instance does not work via blue button
Summary: Creating an MCH instance does not work via blue button
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.12.0
Assignee: Steve Goodwin
QA Contact: Yanping Zhang
Olivia Payne
Depends On:
TreeView+ depends on / blocked
Reported: 2022-06-07 18:11 UTC by kurwang
Modified: 2023-01-17 19:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
* Previously, when installing an Operator that required a custom resource (CR) to be created for use, the *Create resource* button could fail to install the CR because it was pointing to the incorrect namespace. With this update, the *Create resource* button works as expected. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2094502[*BZ#2094502*])
Clone Of:
Last Closed: 2023-01-17 19:49:52 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11949 0 None open Bug 2094502: Fix bug where the create required custom resource button points to the wrong namespace. 2022-08-10 16:15:28 UTC
Github stolostron backlog issues 23051 0 None None None 2022-06-08 00:03:21 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:50:00 UTC

Description kurwang 2022-06-07 18:11:08 UTC
Description of the problem:
When attempting to create an MCH instance using the blue button via the operator ui, it directs me to a blank page

Operator snapshot version: 2.5.0-DOWNSTREAM-2022-05-19-19-49-24

OCP version: 4.8

Browser Info:

Steps to reproduce:
1. Setup the catalog source in acm for it to show in the operatorhub
2. Install ACM via operatorhub
3. Attempt to create an mch instance via the blue button

Actual results:
redirects to a 404 page

Expected results:
show the UI where the mch instance can be created

Additional info:
Similar to this bug https://bugzilla.redhat.com/show_bug.cgi?id=2094466
mch can be created via the providedAPI route

Comment 1 kurwang 2022-06-07 18:25:24 UTC
additional findings
so after testing it out more, this only happens when it isnt the default namespace. If it is in open-cluster-management, the blue button works.

Comment 2 kurwang 2022-06-08 14:51:31 UTC
Reassigning to see if this is an olm issue. During the installation of ACM with downstream snapshot 2.5.0-DOWNSTREAM-2022-05-19-19-49-24 on a non-default namespace
using the blue button to create the instance brings the page to a 404 error.

Comment 5 kurwang 2022-06-08 15:36:54 UTC
Hi apologizes, I worded that poorly. So during an install of the Advanced Cluster Management operator on the operatorhub in a non-default namespace (for example such as ocm instead of the default open-cluster-management), it works. However, when I try to create an multiclusterhub instance via the blue button, it redirects me to do a 404 page. I will provide a picture of what I mean

Attempting to create the mch instance in the Multiclusterhub tab is fine. I think the problem is the page it redirects to is bugged.
Let me know if I need to provide a mustgather still. The version of ocp I am using is 4.8, sorry for the confusion.

Comment 8 kurwang 2022-06-08 15:39:35 UTC
When clicking the blue button, I noticed it changes the namespace from ocm (the namespace I installed the operator) to open-cluster-management (default namespace that doesnt exist in this instance)

Comment 10 kurwang 2022-06-08 16:09:35 UTC
Hi mustgather file was too big to attach, would via email work?

Comment 12 kurwang 2022-06-08 18:51:01 UTC
Still getting the 404 page after clicking the blue button and manually creating the default namespace.

Comment 13 kurwang 2022-06-16 19:22:14 UTC
Hi just trying to followup on this to make sure you weren't waiting on me or anything and wondering what is the status of this.

Comment 16 Jakub Hadvig 2022-06-21 14:39:28 UTC
Is this issue present in 4.11 or 4.10?
Asking since 4.8 is in maintenance mode.

Comment 17 kurwang 2022-06-21 19:23:59 UTC
Hi I do see this issue on ocp 4.10
ACM doesnt support 4.11 so only tested this on 4.10

Comment 18 Steve Goodwin 2022-08-03 20:44:04 UTC
Further investigation...

Upon installation, operators with a required custom resource show an alert (InitializationResourceAlert) which includes a blue button to create the CR (CreateInitializationResourceButton). 
If the operator is installed on any namespace other than the recommended namespace, the create CR button path is broken, because it points to the wrong namespace.

Operator with examples of broken button paths:
Advanced Cluster Management for Kubernetes 
Install on any namespace other than the recommended namespace "open-cluster-management"
The "Create MultiClusterHub" button path is always to /k8s/ns/open-cluster-management/operators.coreos.com...

multicluster engine for Kubernetes 
Install on any namespace other than the recommended namespace "multicluster-engine"
The "Create MultiClusterHub" button path is always to /k8s/all-namespaces/operators.coreos.com....

Comment 20 Yanping Zhang 2022-08-23 08:53:05 UTC
Checked on ocp 4.12 cluster with payload:  4.12.0-0.nightly-2022-08-22-143022.
Steps to Verify the bug:
1.Create a project.
2.Go to OperatorHub page, choose ACM operator to install.
3.On the installation page, for "Installed Namespace", select a namespace, choose the created project, click "Install".
4.When "Create MultiClusterHub" button shows up, click the button, it redirects to the right page.
5.Also try to click "Create MultiClusterHub" button on installed ACM operator details page, it opens the creation page for MultiClusterHub in expected project correctly.
The bug is fixed.

Comment 21 kurwang 2022-08-30 14:05:17 UTC
Hi does the fix also included for "multicluster engine for Kubernetes" with "Advanced Cluster Management for Kubernetes"

Comment 22 Nelson Jean 2022-09-01 03:21:18 UTC
Hi, is this planned to be fixed in OCP 4.11 as well?

Comment 26 errata-xmlrpc 2023-01-17 19:49:52 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: OpenShift Container Platform 4.12.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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