Hide Forgot
[rhel-ospd][upgrade]: There is no rollback mechanism in case overcloud fails in upgrade from 7.3 to 8.0. Environment: ------------ instack-undercloud-2.2.7-2.el7ost.noarch instack-0.0.8-2.el7ost.noarch openstack-heat-templates-0-0.8.20150605git.el7ost.noarch Description: ------------ the upgrade procedure is very sensitive and can take hours, in case there's a failure due to any reason (environment, networking/power outage), there is no rollback mechanism for the overcloud. In order to attempt to overcome the upgrade failure, it will be required to debug each case individually, reach a solution before repeat the last upgrade step that resulted with failure. In case of failure the stack status will switch to: Stack overcloud UPDATE_FAILED.
In the meantime until this is addressed, we should start troubleshooting section in our docs on how get out of various upgrades failures and improve it over time.
per comment 2, moving this to OSP 10. We'll develop and maintain a troubleshooting section in product docs and/or kbase.
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Would this process be applicable to minor updates within a major version as well? For example, would a user be able to use this RFE to rollback an upgrade to OSP13z2 to OSP13z1?
Once the database is touched during major upgrade there is no other way than restoring from snapshot. We could refactor Director to use by default LVM and do snapshots/restores fast or there is already existing procedure for backup and restore.