Comment 0 for bug 1899644

Hello,

A juju status on a kubernetes model was displaying the following:

$ juju status
Model Controller Cloud/Region Version SLA Timestamp
prod-mattermost prodstack-is-2 k8s-is/default 2.8.3 unsupported 13:48:58Z

SAAS Status Store URL
postgresql active prodstack-is-2 admin/prod-mattermost-db.postgresql

App Version Status Scale Charm Store Rev OS Address Notes
mattermost mattermost:v14 active 0/2 mattermost local 28 kubernetes 10.85.2.14

Unit Workload Agent Address Ports Message
mattermost/81 terminated failed 10.87.69.143 8065/TCP unit stopped by the cloud
mattermost/83 active failed 10.87.69.149 8065/TCP
mattermost/84* active failed 10.87.14.57 8065/TCP

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 [0].
As suggested, I deleted the operator pod so it could be restarted but that didn't help.

[0]:https://pastebin.ubuntu.com/p/SytKj5kspt/