Bug 1852388

Summary:	[el7-only] provide playbooks that helps in backing up and restoring node configuration during upgrade
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	gluster-ansible	Assignee:	Gobinda Das <godas>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.5	CC:	agantony, godas, pprakash, puebele, rcyriac, rhs-bugs, sabose, sasundar, satheesaran, sheggodu
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.z Async Update
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gluster-ansible-roles-1.0.5-7.1.el7rhgs	Doc Type:	Enhancement
Doc Text:	Previously, during an RHHI-V upgrade users had to backup a few configurations, reinstall the node, restore the configuration and wait for self-heal to complete before repeating the same steps on the rest of the nodes in the cluster. With this update, this process of upgrade is automated with a playbook that helps backup-restore function smoothly thus minimizing manual errors while backing up and restoring configurations and thus reduces manual effort.	Story Points:	---
Clone Of:	1852369	Environment:
Last Closed:	2020-07-23 04:42:31 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:
Bug Blocks:	1852369

Description SATHEESARAN 2020-06-30 10:29:02 UTC

Description of problem:
-----------------------
While upgrading to RHHI-V 1.8, its not straight as 1.7 was released with RHEL 7 platform. So in this case, user had to backup few configurations and reinstall the node, restore the configuration, and wait for self-heal to complete, before proceeding with the same steps on the rest of the nodes in the cluster

To help in smooth backup-restore, to minimize manual errors while backing up and restoring configurations and to reduce manual efforts, it would be optimal to have playbook that does backup and generates the tar file, which the user can copy to backup node.
Then when the node is reinstalled, user could pull this tar and restore configurations too in an automated way and restart all services.

This way, it will help RHHI users to perform smooth upgrade to 1.8

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

How reproducible:
-----------------
Not applicable as this is not a bug, but the request to include such playbooks

Expected results:
------------------
Automate backup and restore of configuration files

--- Additional comment from RHEL Program Management on 2020-06-30 09:04:38 UTC ---

This BZ is being approved for the RHHI-V 1.8 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'rhhiv‑1.8' and Target Release set to RHHI-V 1.8

Comment 2 SATHEESARAN 2020-06-30 11:13:33 UTC

Playbook to backup the configuration files is not available with RHHI-V 1.7 and for those customers, who wish to migrate
from 1.7 to 1.8, will face difficulty to do this manually.

So this bug becomes evident to supply that playbook in RHHI-V 1.7 with RHV 4.3.11, so that users could make use of this
to upgrade from 1.7 to 1.8

Comment 4 SATHEESARAN 2020-07-06 08:06:47 UTC

Verified with RHVH 4.3.11 and gluster-ansible-roles-1.0.5-7.1.el7rhgs

The required backup and restore playbooks are now available with /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment

[root@ ]# imgbase w
You are on rhvh-4.3.11.1-0.20200701.0+1

[root@ hc-ansible-deployment]# rpm -qa | grep gluster-ansible-roles
gluster-ansible-roles-1.0.5-7.1.el7rhgs.noarch

[root@ hc-ansible-deployment]# ls -1 | grep archive
archive_config_inventory.yml
archive_config.yml

Comment 6 Agil Antony 2020-07-13 16:50:50 UTC

Hi, 

I have updated the doc text. Please review it. 

Thanks,

Comment 7 Gobinda Das 2020-07-14 04:15:29 UTC

RDT looks good to me.

Comment 10 errata-xmlrpc 2020-07-23 04:42:31 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/RHEA-2020:3120