Description of problem: In case anything goes horribly wrong during an FFU upgrade we should provide a method to rollback to the initial state in which the environment was before starting the upgrade. This ticket was filed to keep track of: - undercloud backup before FFU - overcloud backup before FFU - undercloud restore from backup during failed FFU - overcloud restore from backup during failed FFU
Hi Maria, can you set your ack. Thank you.
Hi Carlos, Im moving this RFE to POST since all the review attached is merged. I let you change the status and comment the reason if needed.
Hi, Yeah, all the reviews are merged. If we get further issues we will create additional BZs
https://review.openstack.org/#/c/466213/ is not on stable/queens and not yet proposed stable/queens for tripleoclient Moving back to ASSIGNED to get action on it.
The patch for stable/queens is here && merged: https://review.openstack.org/#/c/550380/
Given this is part of the MVP and it will not run on production, we can remove the blocker flag.
Carlos, I'm confused by https://bugzilla.redhat.com/show_bug.cgi?id=1537054#c15. Can you clarify when this would be run or how we are advocating backup/restore would happen in prod?
The UC backup and restore works now also for FFU. DFG:Metmon will handle the Overcloud backup and restore.
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
Carlos, I think there's some confusion around this BZ and the fixes attached to it so I'd like to clarify, some questions below: 1/ The initial report included both the undercloud and overcloud backup/restore requirement. If I understand it correctly you want to keep track only of the undercloud backup/restore procedure in this bug so if the overcloud backup/restore process should be tracked in a different bug then can we open a new one to keep track of it? 2/ undercloud backup and restore: in case of FFU the undercloud backup should be done before starting the upgrade procedure(when the deployment is still on OSP10). The patches attached to this bug were added to OSP13 so they can only work after the undercloud has been upgraded to 13. Do you plan to backport them to OSP10 to allow the backup to happen before starting the upgrade process?
Hi Marius, Yes, 1/ This BZ is only for tracking the UC backup/restore, we should create another one for the Overcloud steps when they are implemented/tested. 2/ For the fixes we had a few regressions which were tested in >OSP13 for the CLI implementation, and for OSP10 we should follow the manual steps from [1], the regression we had was basically the xattr issue when creating the backup tarball. [1]: https://docs.openstack.org/tripleo-docs/latest/install/controlplane_backup_restore/01_undercloud_backup.html
OK then, I am changing the title to match the expectations. The undercloud backup/restore procedure during FFU(before upgrade) is manual and documented here: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/fast_forward_upgrades/#backing_up_the_undercloud
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, 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-2018:2574