Fix panic when planning orphaned deposed instances #32663
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a highly local fix for a panic which seems to arise when planning orphaned deposed instances. There are two other things to investigate in response to this issue, likely addressing each in follow-up PRs:
readResourceInstanceState
needs to returnnil, nil
in the first place, and redesign it if possible so that we don't have this class of bug elsewhere.(I may have misunderstood an out-of-band discussion about this, and if we might not want to use this approach at all, in which case we'll probably just fix the graph transformers instead.)
Fixes #32645 (probably; we don't have a full reproduction to validate this)
Target Release
1.3.x
This is a panic and a narrowly-scoped fix, so I think we should backport it.
Draft CHANGELOG entry
BUG FIXES