Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
n
nice-airport-15607
09/16/2021, 7:33 PMDoes anyone know how to fix a 409 (An update is in progress for resource) error when there are NO
pending_operationspulumi cancelb
bored-oyster-3147
09/16/2021, 7:42 PMIs the 409 coming from the cloud provider or pulumi?
n
nice-airport-15607
09/16/2021, 8:02 PM@bored-oyster-3147
pulumi upb
bored-oyster-3147
09/16/2021, 8:02 PMyes but is the error coming from AWS API or Pulumi API? Can you share the text?
n
nice-airport-15607
09/16/2021, 8:02 PMyeah i see what you mean, um one second.
@bored-oyster-3147 i see this
someLambda (aws:lambda:Function)
error: 1 error occurred:
* updating urn:pulumi:<stack>::<name>::aws:lambda/function:Function::someLambda: Error modifying Lambda Function Code someLambda-a3069be: ResourceConflictException: The operation cannot be performed at this time. An update is in progress for resource: arn:aws:lambda:us-east-1:<accountId>:function:someLambda-a3069be
status code: 409, request id: 85a622a7-42ab-4e6c-b2cd-23d89205182bb
bored-oyster-3147
09/16/2021, 8:05 PMso that looks like it is coming from AWS. Naturally no pulumi operations will resolve this if it is a response from AWS. So you'll need to either resolve it there or wait for it to finish
n
nice-airport-15607
09/16/2021, 8:07 PMnot sure I’m following, https://www.pulumi.com/docs/troubleshooting/#conflict indicates that its either someone that changed something (which wouldn’t be in my situation, I’m the only dev deploying to this stack), or a bug happened in pulumi…
so what/where would i be able to see the process in aws for what I’m waiting for?
b
bored-oyster-3147
09/16/2021, 8:08 PMPulumi is just surfacing you errors that are coming from AWS. So that would not mean that it is a bug on Pulumi's part, but perhaps that something has changed on the AWS side.
A quick google search returns this forum post that was made today: https://forums.aws.amazon.com/thread.jspa?messageID=995863
n
nice-airport-15607
09/16/2021, 8:09 PMLOL, i’ve been searching for pulumi not aws since the pulumi docs do NOT indicate that we should be looking elsewhere… might be helpful to mention that.
also, i’ve been googling, and that didn’t show up for me, but thx
b
bored-oyster-3147
09/16/2021, 8:10 PMIt might be that Pulumi's AWS Provider needs to be updated to accommodate a change made in the AWS API surface, but Pulumi's AWS Provider is currently a bridge of Terraform's AWS Provider - so if you keep your eyes there, once an update is made there it will quickly bubble to Pulumi's Provider.
n
nice-airport-15607
09/16/2021, 8:12 PMok, yeah i was aware of the terraform, but wasn’t sure if that was aws or pulumi at this point. but thx for the insight, appreciate it
b
bored-oyster-3147
09/16/2021, 8:13 PMPerhaps the log message could better indicate that the error is from the cloud provider. I don't really think the docs need to be updated to reflect that. Anyways, good luck!
n
nice-airport-15607
09/16/2021, 8:13 PMyeah, a better error, or something would be nice to quickly pinpoint
@bored-oyster-3147 i guess the real frustrating part is seeing this
aws lambda get-function --function-name someFunctionName --query 'Configuration.[State, LastUpdateStatus]'
[
"Active",
"Successful"
]b
bored-oyster-3147
09/16/2021, 8:17 PMI'm not sure I understand - what is frustrating?
n
nice-airport-15607
09/16/2021, 8:18 PMit says
Activeso not sure what’s going on here, but something is lost in translation…
b
bored-oyster-3147
09/16/2021, 8:35 PMso I'm not sure how much more I can help you - if the issue is on the AWS side than you may have to seek help elsewhere. I would suggest you try making the change yourself, either via the aws-cli or via the API. If you get the same error, than it is an AWS problem. If you don't get the same error, but Pulumi still does, than you have verified that is a Pulumi problem and probably have the information for opening an issue on github.
n
nice-airport-15607
09/16/2021, 8:41 PMyeah again, i appreciate the help, but when AWS is telling me it’s Active via cli lookup, that kind of pushes this off onto pulumi 🤷 but ill keep digging into it
b
bored-oyster-3147
09/16/2021, 8:47 PMThat assumes that the AWS update endpoint is not failing even though the lambda returned Active, which hasn't been ruled out.