Rollback bay on update failure
This is originally reported in this bug [1], but add rollback support is more like a feature rather than bug fix.
[1] https:/
There is a rollback mechanism in heat after the stack update failed.
There should be a rollback mechanism in magnum after bay update failed.
To implement this, we need to make following change:
In python-magnumclient
Add '--rollback <VALUE>' optional argument to magnum 'bay-update' command, if this argument is set to 'True', bay will rollback on update failure, else if it's set to 'False' or not set, bay will not rollback on update failure, as it is today.
In Magnum:
Add some logic to rollback bay, actually, after bay update failed, if bay rollback was enabled, Heat will rollback
the stack resources. So basically we just need to recover the bay on data model level(i.e. set the value of bay
object fields back to original value if they were updated).
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
WIP: Rollback bay on update failure
