Personally I run undercloud on a vm (kvm) and snapshot it before messing with the heat stack :)
Regards On Tue, Jun 14, 2016 at 6:16 PM, Charles Short <[email protected]> wrote: > Well I just tested this.... > > Tried to create a snapshot of the heat stack overcloud (from a new clean > state). > The snapshot is stuck IN PROGRESS (for over an hour). I cannot remove it. > Perhaps this is not such a good/reliable method. > I will revert to my CloneZilla bare metal imaging to restore back. > > Any other suggestions as to how to cope with a stack update failure > without deleting and recreating the stack? > > Thanks > > Charles > > > On 14/06/2016 16:57, Charles Short wrote: > >> Hi, >> >> TripleO stable Mitaka >> >> I am testing expanding my stack by adding more compute nodes. The first >> update failed, leaving the overcloud stack in a failed state. >> Is it best practice to create a snapshot of the overcloud heat template >> before updating the stack? >> You could then roll back and try the update again. >> >> heat stack-snapshot overcloud >> heat stack-restore [snapshot-id] >> >> Regards >> >> Charles >> >> > -- > Charles Short > Cloud Engineer > Virtualization and Cloud Team > European Bioinformatics Institute (EMBL-EBI) > Tel: +44 (0)1223 494205 > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
