Bug 1846779

Summary:	Replace host workflow from invoked using ansible-playbook, fails to replace the host completely
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	rhhi	Assignee:	Gobinda Das <godas>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	rhhiv-1.8	CC:	rhs-bugs
Target Milestone:	---
Target Release:	RHHI-V 1.8
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gluster-ansible-maintenance-1.0.1-8.el8rhgs	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1846780 (view as bug list)		Environment:
Last Closed:	2020-08-04 14:52:32 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:	1846780, 1848898
Bug Blocks:	1779977

Description SATHEESARAN 2020-06-14 07:47:52 UTC

Description of problem:
-----------------------

Ansible playbook to replace the host was available, but it has few flaws:
1. Host was not replaced correctly
2. Few steps in the playbook are not required
3. Replace brick workflow fails for Nx3 volumes

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gluster-ansible-maintenance-1.0.1-4.el8rhgs

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Create 3 2x3 volumes
2. Reinstall one of the host with fresh setup of bricks
3. Run the replace-host via ansible playbook

Actual results:
---------------
Playbook fails to replace the host

Expected results:
-----------------
Playbook should replace the host successfully


Additional info:

Comment 3 SATHEESARAN 2020-07-10 11:16:48 UTC

verified with gluster-ansible-maintenance-1.0.1-8.el8rhgs

1. Replace host workflow with same FQDN works good
2. Replace host workflow with different host also works good

Comment 4 errata-xmlrpc 2020-08-04 14:52:32 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 (RHHI for Virtualization 1.8 bug fix and enhancement update), 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/RHEA-2020:3314