Bug 1608122 - etcd operator have not be enabled
Summary: etcd operator have not be enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 3.11.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.11.0
Assignee: Sebastien Pahl
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-25 03:05 UTC by ge liu
Modified: 2018-10-11 07:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-11 07:22:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:22:29 UTC

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


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