If I install OpenStack with openstack-installer (autopilot) and the bootstrap for the first environment is launched over the VM that comes with openstack-installer pachage (openstack-installer/tools/vm-batch), landscape service will be installed on a container inside that VM (juju-machine-0-lxc-2 in my case). That container has two IPs (one for the bridge, lxcbr0, and the other one is the actual IP address I supposed to connect, eth0). Whan I execute:

$ JUJU_HOME=~/.cloud-install/ juju ssh landscape/0

from MAAS server, it connects to the VM, instead the container that has landscape.

In the VM, if I execute: sudo lxc-ls -f in every container appears:

NAME                      STATE    IPV4                      IPV6  AUTOSTART
juju-machine-0-lxc-1      RUNNING            -     YES

but in the landscape one appears this way:

NAME                      STATE    IPV4                      IPV6  AUTOSTART
juju-machine-0-lxc-2      RUNNING,  -     YES

( is the bridge IP).

So, basically, when I try to connect to the landscape container, it goes to, instead of My guess is that if I change IPs order that lxc sees, or just get rid of the bridge IP from lxc-ls, would solve the problem. Any ideas?

UPDATE: If I execute:

JUJU_HOME=~/.cloud-install/ juju status | grep -A 4 landscape/0 | grep public-address | awk '{print $2}'"

it gives me the IP, which is the lxcbr0 IP address, instead of the eth0 one. Maybe there is where I have to do some changes.




Thank you for the comment with the LP bug, indeed that does seem to be the issue. Updating to a fixed version of juju with:

sudo apt-add-repository ppa:juju/stable

should fix this odd networking issue.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.