Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1608122 - etcd operator have not be enabled
etcd operator have not be enabled
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd Operator (Show other bugs)
3.11.0
x86_64 Linux
unspecified Severity high
: ---
: 3.11.0
Assigned To: Sebastien Pahl
ge liu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-24 23:05 EDT by ge liu
Modified: 2018-10-11 03:22 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 03:22:06 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:22 EDT

  None (edit)
Description ge liu 2018-07-24 23:05:48 EDT
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 11:26:03 EDT
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 03:05:33 EDT
@ecordell, thanks for your kindly explanation, it's clear to me, now.
Comment 4 errata-xmlrpc 2018-10-11 03:22:06 EDT
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.