Juju 2.X using MAAS, juju status hangs after juju controller reboot

[Imran Khakoo]

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
.local/share/juju/
.cache/juju/
And
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.

[Imran Khakoo (imrankhakoo)]

No takers?

[Tim Penhey (thumper)]

Which actual version of Juju?

The agent should have come up just fine. Are you able to SSH into the controller machine?

If so, go and look in /var/log/juju/machine*.log

It should give some helpful info as to what is going on.

[John A Meinel (jameinel)]

I would think that maybe the IP address of the machine to have changed, and
we are unable to contact the controller at the old IP address. In which
case you would want to edit ~/.local/share/juju/controllers.yaml and update
the known addresses with the new information.

You could also run "juju status --debug" to see what connections the client
is trying to do

On Mon, Jun 26, 2017 at 9:51 AM, Tim Penhey <email address hidden>
wrote:

> Which actual version of Juju?
>
> The agent should have come up just fine. Are you able to SSH into the
> controller machine?
>
> If so, go and look in /var/log/juju/machine*.log
>
> It should give some helpful info as to what is going on.
>
> ** No longer affects: juju-core
>
> ** Changed in: juju
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1697664
>
> Title:
> Juju 2.X using MAAS, juju status hangs after juju controller reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1697664/+subscriptions
>

[Imran Khakoo (imrankhakoo)]

Hi there, this is not a bug. My Juju bootstrap node was a VM that was running on the MAAS server node (the same node I rebooted). Upon reboot, the VM didn't start up automatically and so the "juju status" command hangs. I started the VMs manually and re-added iptables rules. Cloud is functional.