Bug 2124477 - [RFE] Support --db-only option for the overcloud database
Summary: [RFE] Support --db-only option for the overcloud database
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Juan Larriba
QA Contact: Alex Yefimov
URL:
Whiteboard:
: 2121385 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-06 09:29 UTC by Juan Larriba
Modified: 2023-08-07 09:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-10 13:14:30 UTC
Target Upstream Version:
Embargoed:
fdiazbra: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 854620 0 None NEW Add overcloud-db-backup cli playbook 2022-10-07 10:56:36 UTC
OpenStack gerrit 854621 0 None NEW Implement --db-only backups for overcloud 2022-10-07 10:56:38 UTC
Red Hat Issue Tracker OSP-18557 0 None None None 2022-09-06 09:36:00 UTC
Red Hat Knowledge Base (Solution) 6971466 0 None None None 2022-09-08 08:39:08 UTC

Description Juan Larriba 2022-09-06 09:29:59 UTC 
Currently, as of 16.2.2, there is an option to do a backup of the undercloud database using the option "openstack undercloud backup --db-only".

We want also to have this same functionality for overcloud database, so we could take a database backup of one of the nodes of the galera database by using the option "openstack overcloud backup --db-only".
Comment 2 Juan Larriba 2022-09-08 08:39:08 UTC 
*** Bug 2121385 has been marked as a duplicate of this bug. ***
Comment 5 Jesse Pretorius 2022-10-10 13:14:30 UTC 
The references to "openstack overcloud backup --db-only" was an error in documentation which has since been corrected.

The preferred method of backing up the overcloud is the already existing procedure which backs everything up. The backup of only the database has very limited value, and is not high enough on our priority list to formally test and support.
Note You need to log in before you can comment on or make changes to this bug.