Bug 1957613

Summary:	[16.1] Backup and Restore: Backup ansible task fails to start containers and services after undercloud backup failure
Product:	Red Hat OpenStack	Reporter:	Juan Larriba <jlarriba>
Component:	tripleo-ansible	Assignee:	Juan Larriba <jlarriba>
Status:	CLOSED ERRATA	QA Contact:	myadla
Severity:	medium	Docs Contact:
Priority:	high
Version:	16.1 (Train)	CC:	aschultz, elicohen, jbadiapa, jlarriba, myadla, nweinber
Target Milestone:	z7	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tripleo-ansible-0.5.1-1.20210609083311.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1954818	Environment:
Last Closed:	2021-12-09 20:19:09 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:	1954818
Bug Blocks:

Description Juan Larriba 2021-05-06 07:13:12 UTC

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

Description of problem:
Backup and Restore: Backup openstack client integration fails to start containers and services after undercloud backup failure

Any backup failure during undercloud backup doesn't start back containers and services automatically. 

Version-Release number of selected component (if applicable):
RHOS-16.2-RHEL-8-20210420.n.0, tripleo-ansible-0.6.1-2.20210323013845.00f09d9.el8ost.1.noarch

How reproducible: 100%

Steps to Reproduce:
1. Deploy openstack
2. Create an inventory file for your NFS server, undercloud, and overcloud in 
/home/stack/backup-inventory.yaml

3. Install NFS and ReaR on undercloud and overcloud
4. Run Undercloud backup:
openstack undercloud backup --inventory backup-inventroy.yaml
5. Backup failure doesn't start back containers and services automatically.

Actual results: Containers and services get stopped


Expected results: All the containers should be up and running irrespective of undercloud/overcloud backup failure


Additional info:

Comment 24 errata-xmlrpc 2021-12-09 20:19:09 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 (Red Hat OpenStack Platform 16.1.7 (Train) bug fix and enhancement 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-2021:3762