touch-packages team mailing list archive

[Ryan Harper <1510619@xxxxxxxxxxxxxxxxxx>]

Currently looking at updatin lxc package to have lxc-net run After
=network-online.target which should ensure that ifup on auto interfaces
has run, meaning ethX interfaces will have obtained and IP and at that
point then lxc-net can check if something is squating on 10.0.3.X
network and switch to a new one.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1510619

Title:
  Wily: add machine fails using kvm and lxcbr0

Status in juju-core:
  Invalid
Status in lxc package in Ubuntu:
  New

Bug description:
  Juju fails to start a machine after add-machine takes place.

  My environments.yaml:

  local:
    type: local
    container: kvm
    network-bridge: lxcbr0

  Status output:

  ubuntu@ancient-spot:~$ juju status
  environment: local
  machines:
    "0":
      agent-state: started
      agent-version: 1.24.7.1
      dns-name: localhost
      instance-id: localhost
      series: wily
      state-server-member-status: has-vote
    "1":
      agent-state: pending
      instance-id: ubuntu-local-machine-1
      series: wily
      hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M

  debug log:

  http://paste.ubuntu.com/12980615/

  
  I never see anything in the logs which indicate machine-1 is being deployed or what else could be going on with it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions