Bug 1807360

Summary:	etcd static pods laid down by the cluster-etcd-operator should not depend on the etcd cluster API after the first run
Product:	OpenShift Container Platform	Reporter:	Tomáš Nožička <tnozicka>
Component:	Etcd	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4	CC:	alpatel, geliu, sbatsche
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1807054	Environment:
Last Closed:	2020-05-04 11:42:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1807054
Bug Blocks:

Description Tomáš Nožička 2020-02-26 07:47:29 UTC

+++ This bug was initially created as a clone of Bug #1807054 +++

Description of problem:

Etcd static pods laid down by the cluster-etcd-operator should not depend on the etcd cluster API calls after the first successful run (after the corresponding etcd member goes to the started state).

Comment 3 ge liu 2020-03-09 08:04:46 UTC

No Regression issue.

Comment 5 errata-xmlrpc 2020-05-04 11:42:25 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-2020:0581