Bug 1671206

Summary:	Fail to create Cluster Logging Instance via console
Product:	OpenShift Container Platform	Reporter:	Yadan Pei <yapei>
Component:	Management Console	Assignee:	Samuel Padgett <spadgett>
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1.0	CC:	aos-bugs, jokerman, mifiedle, mmccomas
Target Milestone:	---
Target Release:	4.1.0
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:	2019-01-31 12:37:00 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 Yadan Pei 2019-01-31 05:42:18 UTC

Description of problem:
Fail to create Cluster Logging Instance via console through Catalog -> Developer Catalog

Version-Release number of selected component (if applicable):
io.openshift.build.commit.url=https://github.com/openshift/console/commit/5070df1f11d481f36152c0218f209a085eed9d64

How reproducible:
Always

Steps to Reproduce:
1. Subscribe Cluster Logging operator into openshift-operators namespace
Catalog -> Operator Hub -> Cluster Logging -> Install -> Subscribe
2. After cluster logging operator is created, create Cluster Logging Instance via Catalog -> Developer Catalog -> Installed Operators -> Cluster Logging -> Create

Actual results:
2. Blank page returned and hanged

Expected results:
2. Should return successful/error result

Additional info:
$ oc create -f https://raw.githubusercontent.com/openshift/cluster-logging-operator/master/hack/cr.yaml
clusterlogging.logging.openshift.io/example created

Comment 1 Mike Fiedler 2019-01-31 12:37:00 UTC


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