Bug 1671206 - Fail to create Cluster Logging Instance via console
Summary: Fail to create Cluster Logging Instance via console
Keywords:
Status: CLOSED DUPLICATE of bug 1671125
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.1.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-31 05:42 UTC by Yadan Pei
Modified: 2019-03-12 14:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-31 12:37:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.