Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pulumi 3.37.0+ is throwing failed to complete update: [409] #10293

Closed
rshade opened this issue Jul 29, 2022 · 3 comments · Fixed by #10294
Closed

Pulumi 3.37.0+ is throwing failed to complete update: [409] #10293

rshade opened this issue Jul 29, 2022 · 3 comments · Fixed by #10294
Labels
area/backends State storage (filestate/httpstate/etc.) impact/regression Something that used to work, but is now broken kind/bug Some behavior is incorrect or out of spec p1 Bugs severe enough to be the next item assigned to an engineer resolution/fixed This issue was fixed
Milestone
0.76

Comments

@rshade
Copy link
Contributor

rshade commented Jul 29, 2022

What happened?

Pulumi 3.37.0 is throwing an error: error: failed to complete update: [409] Stack 'monitoring-test' is not locked by update id 'eb18fada-43d9-470e-a521-45800a94d5fe' (15gs5q9) when updating a stack. We believe it is from #10168. Rolling back to 3.36.0 is a current workaround.

Steps to reproduce

  1. Create a stack with 3.36.0 with http backend
  2. upgrade to 3.37.0
  3. try to pulumi up the stack.

Expected Behavior

Pulumi up should follow thru and create the stack.

Actual Behavior

Pulumi up throws a 409

Versions used

3.37.0

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
@rshade rshade added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Jul 29, 2022
@mikhailshilkov mikhailshilkov added p1 Bugs severe enough to be the next item assigned to an engineer area/backends State storage (filestate/httpstate/etc.) and removed needs-triage Needs attention from the triage team labels Jul 29, 2022
@mikhailshilkov mikhailshilkov mentioned this issue Jul 29, 2022
Merged
@Frassle
Copy link
Member

Frassle commented Jul 29, 2022

How did none of our testing pick this up?

@mikhailshilkov
Copy link
Member

mikhailshilkov commented Jul 29, 2022 •
edited

@Frassle I believe this issue is with a non-Pulumi http backend

@Frassle
Copy link
Member

Frassle commented Jul 29, 2022

Ah understood, cloud be slight difference in behavior there that triggered this.

@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Jul 29, 2022
@mikhailshilkov mikhailshilkov added this to the 0.76 milestone Jul 29, 2022
@mikhailshilkov mikhailshilkov added the impact/regression Something that used to work, but is now broken label Jul 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/backends State storage (filestate/httpstate/etc.) impact/regression Something that used to work, but is now broken kind/bug Some behavior is incorrect or out of spec p1 Bugs severe enough to be the next item assigned to an engineer resolution/fixed This issue was fixed
Projects
None yet
Milestone
0.76
Development

Successfully merging a pull request may close this issue.

Revert "Remove api/renewLease from startup crit path" pulumi/pulumi
4 participants
@rshade @Frassle @mikhailshilkov @pulumi-bot