Bug 1785102 - Failed to install "Couchbase" operator in project
Summary: Failed to install "Couchbase" operator in project
Keywords:
Status: CLOSED DUPLICATE of bug 1790612
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ISV Operators
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Melvin Hillsman
QA Contact: tonyc
URL:
Whiteboard:
Depends On:
Blocks: 1779858
TreeView+ depends on / blocked
 
Reported: 2019-12-19 07:11 UTC by Yanping Zhang
Modified: 2020-01-24 20:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-24 20:34:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
deployment-status (65.38 KB, image/png)
2019-12-19 07:11 UTC, Yanping Zhang 		no flags Details
error-page (79.44 KB, image/png)
2019-12-19 07:12 UTC, Yanping Zhang 		no flags Details
View All

Description Yanping Zhang 2019-12-19 07:11:25 UTC 
Created attachment 1646322 [details]
deployment-status

Description of problem:
Install "Couchbase" operator in project, the deployment trapped in "UpgradePending", and showed "Failed: Unknown" on CSV page.

How reproducible:
Always

Steps to Reproduce:
1.In operator hub, choose "Couchbase Operator", install it in a project. 
2. Check on "Installed Operators" page.
3. Click into "couchbase-enterprise-certified".

Actual results:
2. The couchbase operator installation doesn't succeed, the deployment is trapped in "UpgradePending".
3. On the CSV overview page, it showes: "Failed: Unknown". And there is no button for instance creation.

Expected results:
2. The operator should be installed successfully.
3. Should no error info. And should have button to create instance.

Additional info:
Comment 1 Yanping Zhang 2019-12-19 07:12:32 UTC 
Created attachment 1646323 [details]
error-page
Comment 2 Melvin Hillsman 2020-01-24 20:34:06 UTC 

*** This bug has been marked as a duplicate of bug 1790612 ***
Note You need to log in before you can comment on or make changes to this bug.