pulumi-aws
pulumi-aws copied to clipboard
Bug/question ResourceNotFoundException: No progress information found
What happened?
We have a pulumi stack that we've been successfully using for over a year. In one of our usual deploys we encountered this error:
aws:elasticsearch:Domain (<domain-name>):
error: 1 error occurred:
* updating urn:pulumi:prod::api::aws:elasticsearch/domain:Domain::<domain-name>: 1 error occurred:
* ResourceNotFoundException: No progress information found
We also see this in our state file initErrors:
"initErrors": [
"updating urn:pulumi:prod::api::aws:elasticsearch/domain:Domain::<domain-name>: 1 error occurred:\n\t* ResourceNotFoundException: No progress information found\n\n"
],
We confirmed that the resource does exist (we can see it in our aws console and in the state file) and we are correctly setting the region. Other resources are able to update with no problem.
Steps to reproduce
Unsure how to reproduce - part of the ask of this question/report is to understand how something like this could happen.
Expected Behavior
We expected the resource to update successfully.
Actual Behavior
Got a ResourceNotFound exception and we are unable to update our stacks.
Output of pulumi about
No response
Additional context
This question was posted recently on stack overflow and describes something very similar to what we are seeing.
We are hoping to understand what would cause this error to happen and steps on how to resolve.
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).
We were able to temporarily get around the issue by using ignoreChanges
to skip the update that fails. However, still looking for a fix for the root issue.
Hi @whwa
Please can you let us know what version of pulumi-aws that you are using? Does a pulumi refresh help in this space?
Paul
I would like to work on this issue. Reply ASAP.
Hi @Prayag-raj-sharma - thank you for your interest in contributing to Pulumi! We're more than happy to help you resolve this issue here. Feel free to get started and reach out with any questions. Thank you!
This issue looks stale with no clear repro details. I'll go ahead and close it. Please open a new one with a full repro and details about the versions, if the issue still persists today.