Bug 1977392
| Summary: | we should recommend taking db backup before running the upgrade prepare command for upgrade to rhosp16.2 from 13 | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jose Luis Franco <jfrancoa> |
| Component: | tripleo-ansible | Assignee: | Jose Luis Franco <jfrancoa> |
| Status: | CLOSED ERRATA | QA Contact: | Jason Grosso <jgrosso> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 16.2 (Train) | CC: | amcleod, asalvati, ccamacho, dhill, hbrock, jbadiapa, jfrancoa, jhajyahy, jpretori, jslagle, kamukher, kmehta, lbezdick, mariel, mburns, mmagr, rhos-docs |
| Target Milestone: | z2 | 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.20220112214927.5e744eb.el8ost python-tripleoclient-12.6.1-2.20220114104840.db6a328.el8ost | Doc Type: | Enhancement |
| Doc Text: |
With this update, you can use the `openstack undercloud backup` command with the `--db-only` option to create a backup of the database that runs on the undercloud node. You can use that backup to recover the state of the database in the event that it becomes corrupted during the upgrade process.
|
Story Points: | --- |
| Clone Of: | 1963347 | Environment: | |
| Last Closed: | 2022-03-23 22:10:48 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: | 1963347 | ||
| Bug Blocks: | |||
|
Comment 6
Jose Luis Franco
2021-10-11 15:02:39 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 (Release of components for Red Hat OpenStack Platform 16.2.2), 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-2022:1001 |