Bug 1835319 - cluster-etcd-operator: host-etcd-2 service can race with endpoints
Summary: cluster-etcd-operator: host-etcd-2 service can race with endpoints
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.5.0
Assignee: Sam Batschelet
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-13 15:20 UTC by Sam Batschelet
Modified: 2020-07-13 17:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:38:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 346 0 None closed Bug 1835319: remove dead host-etcd-2 service 2020-10-02 00:50:49 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:38:44 UTC

Description Sam Batschelet 2020-05-13 15:20:20 UTC
Description of problem: during bootstrap we populate bot a service and endpoints resource for the openshift-etcd namespace. This resource contains the bootstrap IP which is a critical for cluster bootstrap success. In some circumstances if the service is created before the endpoints the endpoints will be created automatically without the bootstap IP.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.create cluster
2.
3.

Actual results: cluster fails as etcd static pod can not communicate with etcd on bootstrap node.


Expected results: endpoints resource contains proper data.


Additional info:

Comment 3 ge liu 2020-06-18 09:15:16 UTC
Run regression test without hit this err.

Comment 4 errata-xmlrpc 2020-07-13 17:38:33 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:2409


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