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

Add log of reload error on every reconciliation #811

Merged
merged 1 commit into from
Jul 6, 2021

Conversation

jcmoraisjr
Copy link
Owner

Improves the visibility of a configuration issue. Currently only reload attempts would lead to a log error if the current state builds an invalid configuration file. This change adds an error log on every reconciliation, being dynamic or not, informing the timestamp when the configuration was broken for the first time, if the configuration is in fact broken. A broken configuration leads to new state not being correctly applied, and should also promote an outage if the controller or haproxy crashes, or the controller restarts.

Improves the visibility of a configuration issue. Currently only reload
attempts would lead to a log error if the current state builds an
invalid configuration file. This change adds an error log on every
reconciliation, being dynamic or not, informing the timestamp when the
configuration was broken for the first time, if the configuration is in
fact broken. A broken configuration leads to new state not being
correctly applied, and should also promote an outage if the controller
or haproxy crashes, or the controller restarts.
@jcmoraisjr
Copy link
Owner Author

#807

@jcmoraisjr jcmoraisjr merged commit 4a0fff4 into master Jul 6, 2021
@jcmoraisjr jcmoraisjr deleted the jm-log-reload-error branch July 6, 2021 00:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants