Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1963347

Summary:	[QE] [Docs] we should recommend taking db backup before running the upgrade prepare command for upgrade to rhosp16.1 from 13
Product:	Red Hat OpenStack	Reporter:	Ketan Mehta <kmehta>
Component:	tripleo-ansible	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	low
Version:	16.2 (Train)	CC:	amcleod, ccamacho, jbadiapa, jgrosso, jhajyahy, jjoyce, joflynn, jpretori, jslagle, kgilliga, mariel, mburns, mmagr, sgolovat
Target Milestone:	z4	Keywords:	Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	tripleo-ansible-0.8.1-2.20220421170338.85e112b.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1977392 (view as bug list)		Environment:
Last Closed:	2024-03-26 12:25:25 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:	1977392

Description Ketan Mehta 2021-05-22 14:19:27 UTC

Description of problem:

It should be called out either through the docs or via the CLI when openstack overcloud upgrade prepare is triggered to capture a database backup of the undercloud at this stage as well.

usually the user would take the db backup before the undercloud leapp upgrade and once the undercloud is upgraded, with updated templates "upgrade prepare" is triggered.

However if there are issues with templates, which can be on multiple occasions in scenarios like:

* incorrect node mapping
* incorrect scheduler hints
* use of deprecated parameters for scheduler hints, etc

It can end up causing issues with the db and some of the nodes might even be cleaned up or spawned extra in heat..failing with no valid hosts etc.

And in order to recover from this situation a db backup would be very easy to go to and correct the incorrect changes, complete the upgrade prepare.

So, a notice about capturing the db dump as soon as the user hits openstack overcloud upgrade prepare or calling it out in the docs under 'upgrade prepare'  section would be a good value addition and help a lot in certain situations in which otherwise one would have to opt to going back to 13 undercloud and do the undercloud upgrade again as well.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 8 Jose Luis Franco 2021-06-29 10:41:56 UTC

Hey @Juan,

Is it OK for you if we leave this BZ as a docs one to update the 16.1.X documentation and I will clone the BZ to try to land the new command in 16.2 z1, does it sound good to you? Then, we will need to document the command also in the 16.2 docs, but we could use the same BZ to adapt the docs.

Comment 9 Juan Badia Payno 2021-06-29 11:00:18 UTC

sure, there is no problem from my side.

Comment 11 Jesse Pretorius 2021-07-29 17:56:26 UTC

@vgrosu Would this be documentation that you update? If not, can you assign this to the appropriate person?

Comment 13 Vlada Grosu 2021-07-30 09:50:31 UTC

Hi Jesse,

I will assign it to myself and create a draft after which I'll ask the B&R DFG and tech writer to review it.

Many thanks,
Vlada 


(In reply to Jesse Pretorius from comment #11)
> @vgrosu Would this be documentation that you update? If not, can
> you assign this to the appropriate person?

Comment 29 Vlada Grosu 2021-08-04 11:58:39 UTC

Thank you for your help folks.

For 16.1, and for 16.2-beta, the docs use the `backup-and-restore` Ansible role to create a backup of the database that runs on the undercloud node.

Here are the published docs:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/framework_for_upgrades_13_to_16.1/index#backup-and-restore
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/framework_for_upgrades_13_to_16.1/index#undercloud-node-database-backup_initial-steps
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/framework_for_upgrades_13_to_16.1/index#upgrade-checklist
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/undercloud_and_control_plane_back_up_and_restore/index#creating-a-database-backup-of-the-undercloud-node_osp-ctlplane-br


https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2-beta/html-single/framework_for_upgrades_13_to_16.2/index#backup-and-restore
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2-beta/html-single/framework_for_upgrades_13_to_16.2/index#undercloud-node-database-backup_initial-steps
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2-beta/html-single/framework_for_upgrades_13_to_16.2/index#upgrade-checklist
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2-beta/html-single/undercloud_and_control_plane_back_up_and_restore/index#creating-a-database-backup-of-the-undercloud-node_osp-ctlplane-br


When OSP 16.2.1 ships (as this BZ has the z1 target milestone), I will publish the version of the docs that uses `openstack undercloud backup` command with the `--db-only` option to create a backup of the database that runs on the undercloud node.

Comment 41 Juan Larriba 2022-04-08 09:48:44 UTC

*** Bug 2071986 has been marked as a duplicate of this bug. ***

Comment 57 errata-xmlrpc 2024-03-26 12:25:25 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.2.6 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-2024:1519