Comment 3 for bug 1999427

The charm's status may appear like this:

aws-k8s-storage/0* error idle 54.80.73.214 hook failed: "update-status"

When the affected charms are deployed on a cloud with a
`kube-api-loadbalancer`, the load-balancer can respond
to client requests with a 502 Gateway Error, among
other error statuses not produced by the API server
itself. The charm's kubernetes client library raises an
unhandled exception in this case. This results is the
charm being in an error state which is easily resolved
by running

  ```bash
  juju resolve <charm/unit>
  ```