Comment 4 for bug 1990369

It turned out there was a stale kubernetes service with the name we were trying to deploy with. The reason was that we had a problem deleting the service due to the following error https://paste.ubuntu.com/p/q4XyRRHmWM/. This was fixed by adding the "load-balancer_observer" role to the relevant account, and then the service deletion completed. We could then redeploy the application with the same name.

As discussed with Ian Booth, we think Juju should include a more useful error message explaining why it can't provision the new application (e.g. because there's a k8s service with a conflicting name).