touch-packages team mailing list archive

[Launchpad Bug Tracker <1510619@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---------------
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
    - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
    - Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
    - Fix ubuntu-cloud template to detect compression algorithm instead
      of hardcoding xz. Also update list of supported releases and use trusty
      as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
    meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
    (LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
     LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber <stgraber@xxxxxxxxxx>  Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
       Status: Fix Committed => Fix Released

** Changed in: lxc (Ubuntu Wily)
       Status: Fix Committed => Fix Released

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

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