Bug 1349712

Summary:	[RFE] Support scale up playbook to add new etcd host
Product:	OpenShift Container Platform	Reporter:	Kenjiro Nakayama <knakayam>
Component:	RFE	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED ERRATA	QA Contact:	Gaoyun Pei <gpei>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	aos-bugs, atolj, bvincell, byount, dmoessne, erich, fcami, ghuang, gpei, jkaur, jokerman, jolee, jrosenta, mark.vinkx, misalunk, mmccomas, mmckinst, nschuetz, pdwyer, pep, pkanthal, robert.bohne, tparsons, trankin
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-05 13:36:17 UTC	Type:	Bug
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:
Bug Blocks:	1267746

Description Kenjiro Nakayama 2016-06-24 05:22:46 UTC

1. Proposed title of this feature request

- Support scale up playbook to add new etcd

3. What is the nature and description of the request?

- Currently there are scaleup master and node playbook, but there are no scaleup playbook for adding new etcd.

4. Why does the customer need this? (List the business requirements here)

- There seems to be no reason why RH doesn't support it even though master and node has the playbook.

5. How would the customer like to achieve this? (List the functional requirements here)

- Same way of adding Master and Node

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

- As far as I checked, there are no such RFE.

9. Is the sales team involved in this request and do they have any additional input?

10. List any affected packages or components.

- installer

Comment 2 Kenjiro Nakayama 2016-06-24 07:33:57 UTC

The subject of this  RFE is "Supported method for adding additional Masters and ectd hosts to HA environment". 

But the bug fix didn't support to add new etcd hosts?

Comment 4 Jason DeTiberus 2016-07-05 14:16:24 UTC

This change requires refactoring the way that we manage etcd, since the way we are currently managing it only affects configuration on first boot.

Comment 5 atolj 2017-02-08 14:10:33 UTC

I found a pull request with a possible solution for this RFE on the github project. https://github.com/openshift/openshift-ansible/pull/3043 
Will this change be enough to solve the feature request?

Comment 9 Gaoyun Pei 2017-10-19 09:06:53 UTC

Verify this bug with openshift-ansible-3.7.0-0.161.0.git.0.2ca2c69.el7.noarch.rpm

Add "new_etcd" as a new sub-group under [OSEv3:children] in ansible inventory file, also specify the new etcd hosts in [new_etcd] sub-group.

#Example inventory file
[OSEv3:children]
masters
nodes
etcd
new_etcd

[OSEv3:vars]
deployment_type=openshift-enterprise
...

[masters]
master

[nodes]
node

[etcd]
etcd-1

[new_etcd]
new-etcd-1
new-etcd-2


Run etcd scale-up playbook:
ansible-playbook -i host /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-etcd/scaleup.yml

After playbook finished, new etcd hosts could be added into existing etcd cluster, also added into etcdClientInfo.urls in master-config.yaml. The new etcd  cluster could work well.

QE have verified this playbook was working well for etcd scale-up from one single external etcd to 3 members ha etcd cluster , or extending from a 3 members etcd cluster to 4 members etcd cluster. And all test passed in rpm_ installed/containerized_installed/system_container_installed ways.

Comment 12 Scott Dodson 2017-12-05 13:36:17 UTC

This RFE was included in the 3.7 GA playbooks and the latest errata of the 3.6 playbooks.

Comment 13 Red Hat Bugzilla 2023-09-14 23:59:42 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days