Yes, that means that you managed to trigger the update bug, i mentioned earlier. Either today or tomorrow we will release an update that will automatically attempt to resolve this. If you dont want to wait you can also:

sudo helm history --kubeconfig /etc/rancher/k3s/k3s.yaml -n united-manufacturing-hub united-manufacturing-hub

The latest revision should say "upgrade pending". Then you can rollback to it:

sudo helm rollback --kubeconfig /etc/rancher/k3s/k3s.yaml -n united-manufacturing-hub united-manufacturing-hub <REVISION>

Afterwards it should resume upgrading