up icon indicating copy to clipboard operation
up copied to clipboard
verified publisher icon apex

The following resource(s) failed to create: [ApiLambdaPermissionProduction, ApiDeploymentStaging, ApiDeploymentProduction, ApiLambdaPermissionStaging]

Open atistler opened this issue 7 years ago • 10 comments

Prerequisites

  • [x] I am running the latest version. (up upgrade)
  • [x] I searched to see if the issue already exists.
  • [ ] I inspected the verbose debug output with the -v, --verbose flag.
  • [ ] Are you an Up Pro subscriber?

Description

I am getting an intermittent error when running up deploy. This error occurs maybe 1/10 deployments. I think it has something to do with Cloudformation trying to update the API Gateway concurrently for each stage. Screenshots attached:

The following resource(s) failed to create: [ApiLambdaPermissionProduction, ApiDeploymentStaging, ApiDeploymentProduction, ApiLambdaPermissionStaging].

Steps to Reproduce

up deploy

stack_detail stack_detail-2

atistler avatar Aug 03 '18 14:08 atistler

interesting, haven't hit that one before, I'll try adding a DependsOn so those two deployments don't happen in parallel, hopefully that'll do the trick. Thanks for the report!

tj avatar Aug 03 '18 23:08 tj

getting a similar error consistently. can't seem to deploy this app at all. Not sure if it is related to this or not.

Error: deploying: us-east-1: The following resource(s) failed to create: [ApiLambdaPermissionProduction, ApiProxyMethod, DnsZoneSaxonincCom, ApiDomainProduction, ApiLambdaPermissionStaging].

tamagokun avatar Sep 04 '18 15:09 tamagokun

@tamagokun if you run up stack there should be some more detailed errors, may be a conflict with an existing domain name or something like that

tj avatar Sep 04 '18 17:09 tj

@tj ok, I see. Sorry to derail this issue!

tamagokun avatar Sep 04 '18 18:09 tamagokun

@tamagokun No worries! Let me know if you hit something that doesn't seem obvious, sometimes the AWS error messages a bit obscure

tj avatar Sep 04 '18 19:09 tj

Any update on this issue?

atistler avatar Sep 10 '18 20:09 atistler

Seems like a bug on their part to me kind of. If they let you define deployments in cloudformation they shouldn't race with each other, I'll try bringing it up with the AWS team if I can't find a decent solution, seems like something they should be retrying internally.

Is there any chance other tools (or the aws console) are making deployments at the same time? Or is it just Up? I haven't hit this yet

tj avatar Sep 11 '18 19:09 tj

Well I have my CI/CD running up so potentially two (or more) could be occurring at the same time. However this would not be occurring for the same up deployment. The CI/CD create new up deployments each time and deletes them when it is done.

atistler avatar Sep 19 '18 14:09 atistler

I get this issue because it's trying to email a developer for the SSL certification request, which can't ever return because I've got no email for this domain, so I just manually created the SSL's, deleted the entire stack, and pushed again...

michaelcuneo avatar Oct 13 '20 07:10 michaelcuneo

I have this issue too. I've tried deleting the stack and recreating without success.

jadbox avatar Dec 17 '20 16:12 jadbox