upgrade-charm --force-units does not upgrade k8s charm

[Stuart Bishop]

A k8s unit was in an error state due to a charm bug. The charm was fixed, and 'juju upgrade-charm --force-units directory' run. Juju reported success: "Added charm "cs:~stub/generik8s-10" to the model".

However, "juju resolved directory/0" did not appear to trigger a new upgrade-charm hook. Further 'juju upgrade-charm' commands fail, as Juju claims the latest version is already deployed. And, interestingly, further 'juju resolved' commands fail, with Juju claiming that the unit is not in an error state. However, 'juju status' disagrees, clearly showing the error state.

ubuntu@blimp:~$ juju upgrade-charm --force-units directory
ERROR already running latest charm "cs:~stub/generik8s-10"

ubuntu@blimp:~$ juju resolved directory/0
ERROR cannot set resolved mode for unit "directory/0": already resolved

ubuntu@blimp:~$ juju status
Model Controller Cloud/Region Version SLA Timestamp
k8smodel localhost-localhost myk8s 2.6.2 unsupported 16:51:52Z

App Version Status Scale Charm Store Rev OS Address Notes
directory error 1 generik8s jujucharms 10 kubernetes hook failed: "upgrade-charm"

Unit Workload Agent Address Ports Message
directory/0 error idle hook failed: "upgrade-charm"

Offer Application Charm Rev Connected Endpoint Interface Role
directory-db directory generik8s 10 1/1 postgres pgsql requirer

[Stuart Bishop (stub)]

The charm had yet to spin up a pod, as it was still attempting (and failing) to setup relations needed for the pod config.