EVEREST-1818 | fix DBEngine status reconciliation #636
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mayank Shah <mayank.shah@percona.com>
mayankshah1607
changed the title
mayankshah1607
requested review from
recharte and
oksana-grishchenko
as code owners
recharte
approved these changes
Jan 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CHANGE DESCRIPTION
Problem:
EVEREST-1818
DBEngine reconciler complains CSV NotFound when reconciling the status.
Cause:
DBEngine reconciler tries to get the CSV based on the
.status.OperatorVersionof the given DBEngine. However, this field is set only after the DB operator deployment is ready. Until then it keeps reporting these not found errors.Solution:
Set the
.status.OperatorVersionfield even if the deployment is not ready.CHECKLIST
Helm chart
Jira
Tests