This message was deleted.
# generals
sparse-intern-71089
08/08/2018, 5:45 PMThis message was deleted.
c
colossal-beach-47527
08/08/2018, 5:46 PMSorry to hear that @purple-appointment-43233, what was the link that you got? We’ll be sure to fix that ASAP. As far as how to handle this state, you just need to do the following:
p
purple-appointment-43233
08/08/2018, 5:46 PMerror: [409] the stack’s resources are in an unknown state due to an interrupted update;
please export the stack, repair any inconsistencies, and import the result
for more information about this error, see https://goo.gl/hCQnhn
c
colossal-beach-47527
08/08/2018, 5:47 PMExport your Stack’s current checkpoint file. This essentially dumps the current known state of your cloud resources.
pulumi stack export > checkpoint.jsonpulumi stack import < checkpoint.jsoncolossal-beach-47527
08/08/2018, 5:47 PMAt that point the “dirty” bit should be cleared. Let me know if you have any other trouble!
p
purple-appointment-43233
08/08/2018, 5:49 PMLooks like that cleared it. But I’m still running into a problem where a very simple AWS deploy appears to be hanging forever making a spotfleetrequest
c
colossal-beach-47527
08/08/2018, 5:50 PMAs far as insight into that, I don’t have any ideas off the top of my head. Some resources do take a very long time to provision.
Any ideas @white-balloon-205?
p
purple-appointment-43233
08/08/2018, 5:50 PMI changed my spotfleetrequest spec to use a new ami and to last for 10 years, and it just hangs attempting to deploy
purple-appointment-43233
08/08/2018, 6:01 PMWeird, after about 5 minutes, AWS barfed saying that the ami doesn’t exist. Which is weird because it’s the latest AWS ECS-optimized ami listed on their website…
purple-appointment-43233
08/08/2018, 6:05 PMWell, retrying until it worked…worked. ¯\_(ツ)_/¯
purple-appointment-43233
08/08/2018, 6:05 PMThanks for your help
w
white-balloon-205
08/08/2018, 6:10 PM
Note that AWS AMI IDs are per-region, so you'll need to make sure you pick the AMI ID that matches the region you are deploying into. You can also use Paramater Store to get this via https://aws.amazon.com/about-aws/whats-new/2018/04/amazon-ecs-provides-ecs-optimized-ami-metadata-via-ssm-parameter/. See https://github.com/pulumi/pulumi-aws/blob/dc0278d889de6d868c7497a473c32b709aa13521/examples/multiple-regions/index.ts#L12 for an example.
white-balloon-205
08/08/2018, 6:11 PM
As for why this takes so long - that seems unexpected - AWS should normally fail these quickly. Possible that SpotFeetRequest doesn't validate these things early until Spot fulfills the request.
p
purple-appointment-43233
08/08/2018, 6:22 PMSweet! It’s getting meta in here. BTW, the example you gave me is no longer syntactically correct, getParameter doesn’t appear to take a second arg, but I did get it working. 🙂
w
white-balloon-205
08/08/2018, 6:42 PM
Yeah - sorry - that example is part of an in-progress PR which also adds the ability to pass that second parameter - but your question reminded me of it as we were discussing this on the PR just yesterday.