Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1813474

Summary:	etcd: list all peers in initial-cluster
Product:	OpenShift Container Platform	Reporter:	Sam Batschelet <sbatsche>
Component:	Etcd	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	geliu, skolicha
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:	1813473	Environment:
Last Closed:	2020-05-04 11:46:21 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:	1813473
Bug Blocks:

Description Sam Batschelet 2020-03-13 22:46:14 UTC

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

Description of problem: if more than 1 IP address is listed for peerURLS we currently only add [0] to initial cluster


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results: list all peers in initial-cluster


Additional info:

Comment 4 ge liu 2020-03-20 04:10:23 UTC

Failed to verify with 4.4.0-0.nightly-2020-03-19-205629 on vsphere cluster, as I comment on this cloned bug on 4.5, the logs show all peers in initial-cluster in the etcd log in 4.5, but the it have not list all peers in ocp 4.4

# oc logs etcd-control-plane-0  -c etcd 

..................
2020-03-20 03:06:01.028998 I | pkg/flags: recognized and used environment variable ETCD_INITIAL_CLUSTER=etcd-bootstrap=https://139.178.76.13:2380,control-plane-0=https://139.178.76.12:2380
2020-03-20 03:06:01.029002 I | pkg/flags: recognized and used environment variable ETCD_INITIAL_CLUSTER_STATE=existing

Comment 12 errata-xmlrpc 2020-05-04 11:46:21 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