Bug 1384647 - [RFE] [EPIC] [tracker] Allow reverting or reviving failed update of overcloud [NEEDINFO]
Summary: [RFE] [EPIC] [tracker] Allow reverting or reviving failed update of overcloud
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1324142 1419753 1419754 1430914
TreeView+ depends on / blocked
 
Reported: 2016-10-13 18:38 UTC by Alexander Chuzhoy
Modified: 2021-01-26 14:57 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
sathlang: needinfo? (ccamacho)


Attachments (Terms of Use)

Description Alexander Chuzhoy 2016-10-13 18:38:23 UTC
rhel-osp-director:   [RFE] Allow reverting or reviving failed update of overcloud.

Currently we instruct the users to backup their setups, so that in the event of a failure during update - they'll be able to go back to the backed up state.

We should having an option to revert the setup back or to revive a failed update.
Thanks.

Comment 1 Jaromir Coufal 2016-10-18 14:31:08 UTC
Better achievable with containerized deployment of OpenStack, we will try to target this request for the same time.

Comment 5 Jaromir Coufal 2016-12-21 16:37:04 UTC
Changing DFG tag to the correct one, based on new DFGs.

Comment 8 Marios Andreou 2017-06-06 11:08:56 UTC
adding Triaged - as we discussed yesterday Carlos work on the undercloud backup/restore can be tracked here

Comment 9 Amit Ugol 2018-01-07 06:32:21 UTC
Carlos, If this is where we track the backup progress, please update here and lets see if we can set a target release. Originally this was for 10, but now it should be for 14.

Comment 10 Sofer Athlan-Guyot 2021-01-26 14:57:06 UTC
Hi,

automatic revert is not yet supported as it depends on when the update fails. Asking again to @ccamacho@redhat.com what backup/restore support here.


Note You need to log in before you can comment on or make changes to this bug.