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.

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

Bug/question ResourceNotFoundException: No progress information found #2107

Closed
whwa opened this issue Aug 23, 2022 · 5 comments
Closed

Bug/question ResourceNotFoundException: No progress information found #2107

whwa opened this issue Aug 23, 2022 · 5 comments
Labels
kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced

Comments

@whwa
Copy link

whwa commented Aug 23, 2022

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).

@whwa whwa added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Aug 23, 2022
@whwa
Copy link
Author

whwa commented Aug 23, 2022

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.

@stack72
Copy link
Contributor

stack72 commented Aug 23, 2022

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

@stack72 stack72 added awaiting-feedback Blocked on input from the author and removed needs-triage Needs attention from the triage team labels Aug 23, 2022
@Prayag-raj-sharma
Copy link

I would like to work on this issue. Reply ASAP.

@kpitzen
Copy link
Contributor

kpitzen commented Mar 31, 2023

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!

@mikhailshilkov mikhailshilkov added resolution/no-repro This issue wasn't able to be reproduced and removed awaiting-feedback Blocked on input from the author labels Jul 28, 2023
@mikhailshilkov
Copy link
Member

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.

@mikhailshilkov mikhailshilkov closed this as not planned Won't fix, can't repro, duplicate, stale Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Development

No branches or pull requests

5 participants