After deploying an Openstack cloud using juju/MaaS, I rebooted the controller by mistake. When it came back up, juju commands were hanging. I know I could delete
juju add-cloud maas environments.yaml juju add-credential maas
And redeploy the cloud, but that doesn't sound like a production-ready system, to have to redeploy the cloud every time a node suffers a reboot.
Any suggestions? I tried backing up the contents of the above folders, re-adding the MAAS credentials and copying the YAML files back into the new cache files, but juju status hangs again. I'm guessing the SSH keys would have changed as well, after adding a new cloud.