[controller] Fix bug with unexpected LLV Failed statuses and phantom resourses #84
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.
Description
Fix the bug with unexpected LLV resources status Failed updates due to the cache was late to update itself.
Also, this cause to phantom LLV resources with status Created, though an actual LV on a node was removed.
Why do we need it, and what problem does it solve?
Less bad triggers due to scheduling pods, more consistent and valid data.
What is the expected result?
LLV resources do not get Failed status update. Neither phantom ones occur.
Checklist