touch-packages team mailing list archive

[Chris J Arges <1510619@xxxxxxxxxxxxxxxxxx>]

Hello Adam, or anyone else affected,

Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
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:
  Fix Released
Status in lxc source package in Vivid:
  Fix Committed
Status in lxc source package in Wily:
  Fix Committed

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