I tried in another way deploying charms to lxc containers in a MAAS provider. I noticed that the containers are started and got an ip address but juju status remains as "Waiting for agent initialization to finish" $juju status [Services] NAME STATUS EXPOSED CHARM ceph unknown false cs:xenial/ceph-1 glance active false cs:xenial/glance-1 juju-gui unknown false cs:trusty/juju-gui-54 keystone active false cs:xenial/keystone-1 lxd true cs:xenial/lxd-1 mysql unknown true cs:trusty/mysql-38 nova-cloud-controller active true cs:xenial/nova-cloud-controller-1 nova-compute active true cs:xenial/nova-compute-1 openstack-dashboard terminated true cs:xenial/openstack-dashboard-1 rabbits active false cs:xenial/rabbitmq-server-1 redis unknown false cs:trusty/redis-0 wordpress unknown false cs:trusty/wordpress-4 [Relations] SERVICE1 SERVICE2 RELATION TYPE ceph ceph mon peer glance glance cluster peer glance keystone identity-service regular glance lxd container subordinate glance mysql shared-db regular glance nova-cloud-controller image-service regular glance nova-compute image-service regular glance rabbits amqp regular keystone keystone cluster peer keystone lxd container subordinate keystone mysql shared-db regular keystone nova-cloud-controller identity-service regular lxd lxd lxd-migration peer lxd nova-cloud-controller juju-info regular lxd nova-compute lxd regular lxd rabbits juju-info regular mysql mysql cluster peer mysql nova-cloud-controller shared-db regular nova-cloud-controller lxd container subordinate nova-cloud-controller nova-cloud-controller cluster peer nova-cloud-controller nova-compute cloud-compute regular nova-cloud-controller rabbits amqp regular nova-compute lxd lxd subordinate nova-compute nova-compute compute-peer peer nova-compute rabbits amqp regular rabbits lxd container subordinate rabbits rabbits cluster peer wordpress wordpress loadbalancer peer [Units] ID WORKLOAD-STATUS JUJU-STATUS VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE ceph/0 unknown allocating 2/lxd/0 Waiting for agent initialization to finish glance/0 active idle 2.0-beta7 2 9292/tcp 10.1.0.5 Unit is ready lxd/3 active idle 2.0-beta7 10.1.0.5 Unit is ready juju-gui/0 unknown idle 2.0-beta7 0 80/tcp,443/tcp 10.1.0.2 keystone/1 active idle 2.0-beta7 1 10.1.0.4 Unit is ready lxd/0 active idle 2.0-beta7 10.1.0.4 Unit is ready mysql/0 unknown idle 2.0-beta7 0 3306/tcp 10.1.0.2 nova-cloud-controller/0 active idle 2.0-beta7 1 8774/tcp 10.1.0.4 Unit is ready lxd/2 active idle 2.0-beta7 10.1.0.4 Unit is ready nova-compute/0 active idle 2.0-beta7 2 10.1.0.5 Unit is ready lxd/5 active idle 2.0-beta7 10.1.0.5 Unit is ready openstack-dashboard/0 terminated executing 2.0-beta7 2 80/tcp,443/tcp 10.1.0.5 (stop) lxd/1 active idle 2.0-beta7 10.1.0.5 Unit is ready rabbits/0 active idle 2.0-beta7 1 10.1.0.4 Unit is ready lxd/4 active idle 2.0-beta7 10.1.0.4 Unit is ready redis/0 unknown allocating 2/lxc/1 Waiting for agent initialization to finish wordpress/0 unknown allocating 2/lxc/0 Waiting for agent initialization to finish [Machines] ID STATE DNS INS-ID SERIES AZ 0 started 10.1.0.2 4y3h7r trusty default 1 started 10.1.0.4 4y3h7s xenial default 2 started 10.1.0.5 4y3h7w xenial default 5 error pending xenial $juju status --format=yaml redis: charm: cs:trusty/redis-0 exposed: false service-status: current: unknown message: Waiting for agent initialization to finish since: 01 Jun 2016 05:48:08-04:00 units: redis/0: workload-status: current: unknown message: Waiting for agent initialization to finish since: 01 Jun 2016 05:48:08-04:00 juju-status: current: allocating since: 01 Jun 2016 05:48:08-04:00 machine: 2/lxc/1 wordpress: charm: cs:trusty/wordpress-4 exposed: false service-status: current: unknown message: Waiting for agent initialization to finish since: 01 Jun 2016 05:42:36-04:00 relations: loadbalancer: - wordpress units: wordpress/0: workload-status: current: unknown message: Waiting for agent initialization to finish since: 01 Jun 2016 05:42:36-04:00 juju-status: current: allocating since: 01 Jun 2016 05:42:36-04:00 machine: 2/lxc/0 ## but when i ssh into node 2 , i noticed that containers are running and have an valid ip $sudo lxc-ls --fancy NAME STATE AUTOSTART GROUPS IPV4 IPV6 juju-machine-2-lxc-0 RUNNING 1 - 10.1.0.6 - juju-machine-2-lxc-1 RUNNING 1 - 10.1.0.8 - juju-trusty-lxc-template STOPPED 0 - - - ## I think juju agent didn't report ## Where can i check juju machine logs?