yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1569018@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 0.7.7~bzr1208-0ubuntu1

---------------
cloud-init (0.7.7~bzr1208-0ubuntu1) xenial; urgency=medium

  * New upstream snapshot.
    - phone_home: allow usage of fqdn (LP: #1566824) [Ollie Armstrong]
    - chef: straighten out validation_cert and validation_key (LP: #1568940)
    - skip bridges when generating fallback networking (LP: #1569974)
    - rh_subscription: only check subscription if configured (LP: #1536706)
    - SmartOS, CloudSigma: fix error when dmi data is not availble
      (LP: #1569469)
    - DataSourceNoCloud: fix check_instance_id when upgraded (LP: #1568150)
    - lxd: adds basic support for dpkg based lxd-bridge
      configuration. (LP: #1569018)
    - centos: Ensure that a resolve conf object is written as a string.
      (LP: #1479988)

 -- Scott Moser <smoser@xxxxxxxxxx>  Wed, 13 Apr 2016 13:19:03 -0400

** Changed in: cloud-init (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1569018

Title:
  [FFe] support lxc bridge configuration

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  recent changes to lxd added configuration of the lxd bridge.
  We'd like to enable that in cloud-init.

  The change allows the user to put config in cloud-config that will
  basically map to the debconf keys and thus configure their lxd bridge
  and lxd init on first boot  making it immediately useful.

  it should be safe for regression in that if there is no lxd bridge
  config, no change in code path will be taken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1569018/+subscriptions