Kubernetes errors aren't surfaced by Juju
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
I am working on a charm, and ran into a situation where the workload pod wouldn't come up due to an error on my part that I fixed. However, it would be really useful for Juju to surface errors like this, so that charm authors don't have to poke around in the Kubernetes infrastructure to figure out what went wrong.
The particular error in this case was shown by `kubectl describe -nkubeflow replicasets`, which showed these events:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedCreate 10m (x19 over 32m) replicaset-
`juju status` on the other hand, just showed this:
istio-pilot/0* waiting idle waiting for container
It would be nice if `juju status` could at least show something like this:
istio-pilot/0* waiting error ReplicaSet error, see replicasets/
In general, I think that Juju wants to abstract the underlying cloud details away from an operator.
But I think this falls under the general umbrella of making it easier to debug charms, possibly with an additional level of logging and messaging beyond what we'd ordinarily display.
Added a "charm-debugging" tag so that we can find this, and also added to the wishlist.