need mechanism to report error when action-pruner is dead
Bug #2009879 reported by
Tianqi Xiao
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
We have a model under an HA controller (version 2.9.38.1). The action-pruner of this model is not running on any of these controllers. The engine report shows the following messages:
```
report:
...
```
We were expecting to see an error reported by the `/health` endpoint, but there were none.
```
$ curl -k https:/
running
running
running
```
It would be proper to consider the engine status when evaluating controller's health and the `/health` endpoint should report on this kind of failures.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
Revision history for this message
| Joseph Phillips (manadart) wrote | #2 |
Revision history for this message
| Juan M. Tirado (tiradojm) wrote | #3 |
| Changed in juju: | |
| status: | New → Invalid |
Revision history for this message
| Ian Booth (wallyworld) wrote | #4 |
| Changed in juju: | |
| importance: | Undecided → Wishlist |
| status: | Invalid → Triaged |
| summary: |
- /health endpoint doesn't report error when action-pruner is dead + need mechanism to report error when action-pruner is dead |
To post a comment you must log in.
The /health endpoint is quite simple and reflects a binary status - can the controller serve api requests. It can, so comes back healthy. An error would indicate that the controller itself is totally broken, which is not the case.
Tools like the engine report can be access via the introspection api to provide extra detail on the state of various components. Development work is currently underway on a "controller" charm which will provide various endpoints to expose this type of information.