This message was deleted.
# generals
sparse-intern-71089
08/23/2018, 11:21 AMThis message was deleted.
m
microscopic-florist-22719
08/23/2018, 2:33 PM
What is it hung on?
microscopic-florist-22719
08/23/2018, 2:37 PM
(assuming it’s still hung)
t
tall-librarian-49374
08/23/2018, 2:50 PMIt is still. I don't know... It was deleting Lambda Function's, that the last operation, but it shows nothing active.
m
microscopic-florist-22719
08/23/2018, 3:13 PM
Okay. Another approach to recovering from an interrupted update is to export the stack’s raw checkpoint, edit it, and import it. This should only be necessary if there is in fact an operation that is still running, so I think you should be able to kill the update without incident here.
microscopic-florist-22719
08/23/2018, 3:14 PM
Or in other words, I think you may be able to kill the update and start a new one without any issue in this particular case. If that turns out not to be true, please let me know.
t
tall-librarian-49374
08/23/2018, 3:27 PMOk, thanks
tall-librarian-49374
08/23/2018, 3:28 PMInteresting... I pressed Ctrl-C once and it resumed deleting things
m
microscopic-florist-22719
08/23/2018, 3:36 PM
That's supremely odd. I wonder if it was sitting around waiting for console input for some reason?
microscopic-florist-22719
08/23/2018, 3:36 PM
Which cloud/clouds were you targeting?
microscopic-florist-22719
08/23/2018, 3:36 PM
AWS alone?
t
tall-librarian-49374
08/23/2018, 3:56 PMyes
tall-librarian-49374
08/23/2018, 3:56 PMNow it completed
tall-librarian-49374
08/23/2018, 3:57 PMJust in case, I was deleting 481 resources 😋