+++ 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:
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