Open hognevevle opened 1 year ago
Have also experienced this with other resources, described in another issue. Sorry if I opened this issue in the wrong repo.
Hey. Thanks for filing this and the extra context. It seems really tricky.
From my read of it, it sounds like an azure native issue so I'm going to transfer this issue to azure-native.
Side-note: If you're comfortable with terminal text editors, there's an experimental command called pulumi state edit
that could potentially make it easier to pulumi state delete
multiple resources.
Hi @hognevevle. Thanks for reporting this issue. This repo (https://github.com/pulumi/pulumi-azure-native) is the correct place for this issue.
What happened?
Hi there, this has become somewhat of a constantly returning issue for us. As far as I can understand, this happens after a deployment where our built app fails to start in App Services. After some retries, the App Service and Service Farm gets deleted from Azure, which causes issues in Pulumi.
Despite
pulumi refresh
, Pulumi still tries to make changes to this non-existing resource, and fails to recover.The only working solution has been to run
pulumi state delete "<urn>"
to clear out the stale resources.Expected Behavior
pulumi refresh
to detect that the resources no longer exists, and subsequently recreate them in a followingpulumi up
.Steps to reproduce
Provision the resources for an Azure App Services instance, and deploy a failing app to it. It will eventually get torn down by Azure, at which point the Pulumi state is inconsistent and fails to recover.
Output of
pulumi about
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).