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

Changing log level with juju config didn't restart the service #87

Closed
przemeklal opened this issue Nov 8, 2023 · 1 comment · Fixed by #137
Closed

Changing log level with juju config didn't restart the service #87

przemeklal opened this issue Nov 8, 2023 · 1 comment · Fixed by #137
Assignees
Labels
bug Something isn't working
Milestone

Comments

@przemeklal
Copy link
Member

Similarly to issue #86, hardware-exporter config-changed on an unhealthy unit (blocked/idle) didn't trigger service restart.

Hypothetically, if I passed the wrong configuration with juju config and it caused a crash of hardware-exporter, I would be unable to restart it after fixing the config with juju config again.

@Pjack Pjack added the bug Something isn't working label Nov 9, 2023
@Pjack Pjack added this to the 23.10.2 milestone Nov 30, 2023
@jneo8
Copy link
Contributor

jneo8 commented Dec 4, 2023

Auto restart service if tool resource checks and relation exists on update_status hook in #119

@jneo8 jneo8 self-assigned this Dec 4, 2023
@Pjack Pjack linked a pull request Dec 26, 2023 that will close this issue
@Pjack Pjack closed this as completed Dec 26, 2023
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 a pull request may close this issue.

3 participants