Hi all As of last Friday I ve started getting an error anyti

Question

Hi all As of last Friday I ve started getting an error anytime I try to create or update a Lambda function gt Error creating Lambda function ResourceConflictException Function already exist Here are relevant log entries from a Pulumi update that shows a ResourceConflictException happens 5 seconds before the successful deployment possibly suggesting an issue with timeouts and retries ``` timestamp message 2020 05 05 18 07 15 676 eventVersion 1 05 userIdentity type IAMUser principalId AIDA3SNA767QOR3RN3I4Y arn arn aws iam 795443460064 user chad ort snopes local accountId 795443460064 accessKeyId AKIA3SNA767QJLIPDJSB userName chad ort snopes local eventTime 2020 05 05T17 50 10Z eventSource eventName CreateFunction20150331 awsRegion us west 2 sourceIPAddress 97 114 75 236 userAgent aws sdk go 1 29 7 go1 13 8 darwin amd64 APN 1 0 HashiCorp 1 0 Terraform 0 11+compatible + requestParameters functionName lambda test 2d7ed19 runtime nodejs12 x role arn aws iam 795443460064 role lambda test f532b55 handler index handler code description write events to queue and return 200 timeout 180 memorySize 128 publish false environment responseElements functionName lambda test 2d7ed19 functionArn arn aws lambda us west 2 795443460064 function lambda test 2d7ed19 runtime nodejs12 x role arn aws iam 795443460064 role lambda test f532b55 handler index handler codeSize 7957025 description write events to queue and return 200 timeout 180 memorySize 128 lastModified 2020 05 05T17 50 10 334+0000 codeSha256 Hcc9msmvBw+tYRsWLEEf1wItAJ6UEbRtCXg6QwD49ds= version $LATEST environment tracingConfig mode PassThrough revisionId 275fde3f 46de 4790 bd08 90f2be49e309 state Active lastUpdateStatus Successful requestID 37d15659 0d93 4586 80ba dfce76c82a94 eventID 47ff845a 105f 4d51 a06b 5c82bed05e57 eventType AwsApiCall recipientAccountId 795443460064 2020 05 05 18 07 10 282 eventVersion 1 05 userIdentity type IAMUser principalId AIDA3SNA767QOR3RN3I4Y arn arn aws iam 795443460064 user chad ort snopes local accountId 795443460064 accessKeyId AKIA3SNA767QJLIPDJSB userName chad ort snopes local eventTime 2020 05 05T17 51 04Z eventSource eventName CreateFunction20150331 awsRegion us west 2 sourceIPAddress 97 114 75 236 userAgent aws sdk go 1 29 7 go1 13 8 darwin amd64 APN 1 0 HashiCorp 1 0 Terraform 0 11+compatible + errorCode ResourceConflictException errorMessage Function already exist lambda test 2d7ed19 requestParameters functionName lambda test 2d7ed19 runtime nodejs12 x role arn aws iam 795443460064 role lambda test f532b55 handler index handler code description write events to queue and return 200 timeout 180 memorySize 128 publish false environment responseElements null requestID 6f0ea757 b48e 4f43 8de2 0d92be3bd2c3 eventID a3e9e0ac 643a 41e4 acb4 e26330d9c213 eventType AwsApiCall recipientAccountId 795443460064 ``` Additional known info

faint-table-42725 · Answer

I m not able to reproduce this w the code you provided For example I changed the description in an update and that worked as expected

faint-table-42725 · Answer

Deployments using the same stack branch and AWS credentials from other machines connections do not face the same error is an interesting detail

faint-table-42725 · Answer

Does this occur in new projects on the same machine

clever-night-98510 · Answer

Yeah I don t think its my machine at this point since I ve refreshed or updated everything I also had one successful deployment earlier today when I stripped out most of our codebase to start from a simple baseline I moved on thinking I had that but haven t been able to get a successful deployment since