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

[controller] Fix bug with unexpected LLV Failed statuses and phantom resourses #84

Merged
merged 4 commits into from
Aug 29, 2024

Conversation

ViktorKram
Copy link
Contributor

@ViktorKram ViktorKram commented Aug 19, 2024

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

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Signed-off-by: Viktor Kramarenko <[email protected]>
@ViktorKram ViktorKram added the bug Something isn't working label Aug 19, 2024
@ViktorKram ViktorKram self-assigned this Aug 19, 2024
@ViktorKram ViktorKram marked this pull request as draft August 21, 2024 15:17
Signed-off-by: Viktor Kramarenko <[email protected]>
@ViktorKram ViktorKram force-pushed the v-kramarenko-fixes-bug branch 6 times, most recently from 1f2432c to b934a7d Compare August 23, 2024 08:15
@ViktorKram ViktorKram changed the title added command running time count [controller] Fix bug with unexpected LLV Failed statuses and phantom resourses Aug 23, 2024
@ViktorKram ViktorKram force-pushed the v-kramarenko-fixes-bug branch from b934a7d to a9a15bf Compare August 23, 2024 09:05
@ViktorKram ViktorKram requested a review from AleksZimin August 23, 2024 09:07
@ViktorKram ViktorKram marked this pull request as ready for review August 23, 2024 09:07
@ViktorKram ViktorKram force-pushed the v-kramarenko-fixes-bug branch 2 times, most recently from e97f89c to 7ae6236 Compare August 23, 2024 09:14
Signed-off-by: Viktor Kramarenko <[email protected]>
@ViktorKram ViktorKram force-pushed the v-kramarenko-fixes-bug branch 2 times, most recently from 88356f6 to 62a55b0 Compare August 29, 2024 09:15
Signed-off-by: Viktor Kramarenko <[email protected]>
@ViktorKram ViktorKram force-pushed the v-kramarenko-fixes-bug branch from 62a55b0 to 82bd50e Compare August 29, 2024 09:16
@AleksZimin AleksZimin merged commit f1a9e13 into main Aug 29, 2024
7 checks passed
@AleksZimin AleksZimin deleted the v-kramarenko-fixes-bug branch August 29, 2024 09:19
ViktorKram added a commit that referenced this pull request Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants