Bug 1608122

Summary:	etcd operator have not be enabled
Product:	OpenShift Container Platform	Reporter:	ge liu <geliu>
Component:	Etcd	Assignee:	Sebastien Pahl <spahl>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, decarr, dma, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.11.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-11 07:22:06 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 ge liu 2018-07-25 03:05:48 UTC

Description of problem:

as title, installed ocp 3.11 with olm enabled, after installation, there is not etcd opeartor exists in cluster.

ocp version: v3.11.0-0.9.0

How reproducible:
Always

Steps to Reproduce:
install ocp with olm enabled with config:

openshift_enable_olm: true
openshift_management_install_management: ture
after installed, could find olm pod in running status, but there is not etcd-operator pods exist.

Actual results:
as title

Expected results:
etcd-operator should be ready after installtion

Comment 1 Evan Cordell 2018-08-22 15:26:03 UTC

The etcd operator requires additional steps to enable. It is not installed by default when OLM is installed.

Installing OLM should enable the Operator UI in openshift console. From there you can look at "Catalog Sources", find "etcd" and "Subscribe" to it. Subscribing to etcd will ultimately result in the etcd operator running in the same namespace the Subscription was created.

Comment 2 ge liu 2018-08-23 07:05:33 UTC

@ecordell, thanks for your kindly explanation, it's clear to me, now.

Comment 4 errata-xmlrpc 2018-10-11 07:22:06 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, 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/RHBA-2018:2652