juju add-machine kvm:0 not working with maas

Bug #1281994 reported by Christian Bayle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Incomplete
Undecided
Unassigned

Bug Description

After juju add-machine kvm:0
container is staying eternally in pending state

juju destroy-machine keep the container in pending and never dies

juju status
environment: maas
machines:
  "0":
    agent-state: started
    agent-version: 1.17.3.1
    dns-name: g-l5.maas.rd.francetelecom.fr
    instance-id: /MAAS/api/1.0/nodes/node-a6714c4e-7df9-11e3-9d6d-001a6411113a/
    series: trusty
    containers:
      0/kvm/0:
        instance-id: pending
        life: dying
        series: trusty
      0/kvm/1:
        instance-id: pending
        series: trusty
services: {}
admrsc@g-virtual05:~/gocode/src/launchpad.net$

libvirt is not installed in machine '0' and installing it doesn't solve anything

Cheers

Revision history for this message
Curtis Hovey (sinzui) wrote :

Can you confirm that ssh is working (bug 1256615) and that a firewall is not blocking juju (bug 998238)

tags: added: add-machine local-provider
tags: added: maas-provider
Changed in juju-core:
status: New → Incomplete
Revision history for this message
Christian Bayle (bayle-debian) wrote :

It's fixed in trunk, but still I have to manually bring up br0
same as Bug #1271144

Revision history for this message
Christian Bayle (bayle-debian) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.