hey, yesterday we experienced some issues with deployments on our review stacks that seem to have been caused by 3.249 pulumi version. most of the issues related to this seem to have been resolved by now 🙌 however, I still have an issue that I’m not sure if it’s related or not. yesterday, I did

pulumi cancel

on a stack which update took forever. the update was canceled but the deployment it was a part of was still marked as in progress instead of failed. I ran

pulumi destroy

from my machine which succeeded. But then

pulumi stack rm

failed with

error: [403] You do not have permission to perform this operation.

Neo agent suggested that this zombie deployment is probably the cause of that. But later this deployment got eventually marked as failed and I still got the same result. Moreover, when I run pulumi deployment on this stack by doing action -> destroy from the dashboard, which deletes the stack after it destroys it (at least for review stacks), it fails in the same way. Is there a way to remedy this? Additionally, I have a bunch more “undeletable” stacks like this from weeks and months ago, so this might be unrelated to the havoc with our updates suddenly running for 2 hours yesterday. Before, I thought that without administrator role in the organization I might not be able to delete review stacks for some reason and that is the cause. but would it kind of inherit this behavior when I trigger destroy deployment from the dashboard like that? idk, this doesn’t seem that probable after all. The reason I wanted to delete these review stacks “manually” in the first place was because github integration haven’t triggered destroy+remove for those.

👋 would you mind emailing support@pulumi.com with your org, project, and stack details (or the URLs to the stuck deployments?) - we can take a look and get these unstuck if needed

alright. will do just that!