juju agent failed on a kubernetes charm
Bug #1899644 reported by
Benjamin Allot
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Hello,
A juju status on a kubernetes model was displaying some errors [0].
Besides the "terminated" unit, the agent is "failed" on both current units, preventing any "juju run" to complete.
When displaying the logs of the operator pod, we have a constant flow of errors [1].
As suggested, I deleted the operator pod so it could be restarted but that didn't help.
[0]: https:/
[1]: https:/
description: | updated |
description: | updated |
To post a comment you must log in.
Something clearly went wrong, but it's unclear from the pastebins what it was :-/
Can you attach a juju crashdump, and also take a look at free disk, memory, etc. on the machines with the failed units? It feels like there might be an underlying issue on the machine, which Juju is not messaging clearly about.