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

Avoid updating the association status when no association #4986

Conversation

thbkrkr
Copy link
Contributor

@thbkrkr thbkrkr commented Oct 21, 2021

Resolves #4985.

@thbkrkr thbkrkr added >bug Something isn't working v1.9.0 labels Oct 21, 2021
Copy link
Collaborator

@pebrc pebrc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Do we have a unit test that covers this case?

@thbkrkr
Copy link
Contributor Author

thbkrkr commented Oct 21, 2021

Do we have a unit test that covers this case?

No, I will add one.

@thbkrkr thbkrkr merged commit 57b4555 into elastic:master Oct 21, 2021
thbkrkr added a commit to thbkrkr/cloud-on-k8s that referenced this pull request Oct 21, 2021
This fixes a bug where the association status of the Elasticsearch resource is updated by the EsMonitoring association controller when there is no association and therefore no changes to be made. The `oldStatus` and the `newStatus` appeared to be different because one was nil and the other was empty. The equality tests now supports this situation.
thbkrkr added a commit that referenced this pull request Oct 25, 2021
)

This fixes a bug where the association status of the Elasticsearch resource is updated by the EsMonitoring association controller when there is no association and therefore no changes to be made. The `oldStatus` and the `newStatus` appeared to be different because one was nil and the other was empty. The equality tests now supports this situation.
@thbkrkr thbkrkr deleted the skip-association-reconciliation-when-no-association branch November 3, 2021 15:15
fantapsody pushed a commit to fantapsody/cloud-on-k8s that referenced this pull request Feb 7, 2023
This fixes a bug where the association status of the Elasticsearch resource is updated by the EsMonitoring association controller when there is no association and therefore no changes to be made. The `oldStatus` and the `newStatus` appeared to be different because one was nil and the other was empty. The equality tests now supports this situation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug Something isn't working v1.9.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

es-monitoring-association controller should not update the status when no association
2 participants