juju agent failed on a kubernetes charm

[Benjamin Allot]

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://pastebin.ubuntu.com/p/XbfrHpHcrk/
[1]: https://pastebin.ubuntu.com/p/SytKj5kspt/

[Pen Gale (pengale)]

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.

[Ian Booth (wallyworld)]

This looks like it could be bug 1898792 that is fixed in 2.8.6

There's no suggestion it's anything on the underlying machine, disk etc.

If it is the issue in the referenced bug, there's not a great deal that can be done until 2.8.6 comes out, hopefully next week.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.