Comment 17 for bug 1594720

Revision history for this message
Alex (stojimir) wrote :

I seem to be experiencing this same symptom ...

Trying to start a container on a machine with already deployed charm, fails to start a container with a different charm

Machine State DNS Inst id Series AZ Message
0 started 135.111.102.193 c637fs xenial default Deployed

neutron-gateway/0* blocked idle 0 135.111.102.193 Missing relations: messaging, network-service

0/lxd/1 down pending xenial can't get info for image 'juju/xenial/amd64': not found

Juju agent version 2.3.4
MAAS version: 2.3.1 (6470-g036d646-0ubuntu1~16.04.1