yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1568150@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: Confirmed => 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/1568150

Title:
  xenial lxc containers not starting

Status in cloud-init:
  Fix Committed
Status in juju-core:
  Incomplete
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  When deploying a xenial lxc container to a xenial host, the container
  fails during cloud-init with the following error in the container's
  /var/log/cloud-init-output.log:

  2016-04-08 21:07:05,190 - util.py[WARNING]: failed of stage init-local
  failed run of stage init-local
  ------------------------------------------------------------
  Traceback (most recent call last):
    File "/usr/bin/cloud-init", line 515, in status_wrapper
      ret = functor(name, args)
    File "/usr/bin/cloud-init", line 250, in main_init
      init.fetch(existing=existing)
    File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 318, in fetch
      return self._get_data_source(existing=existing)
    File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 227, in _get_data_source
      ds.check_instance_id(self.cfg)):
    File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceNoCloud.py", line 220, in check_instance_id
      dirs=self.seed_dirs)
  AttributeError: 'DataSourceNoCloudNet' object has no attribute 'seed_dirs'

  Trusty containers start just fine.

  Using juju 1.25.5 and MAAS 1.9.2

  Commands to reproduce:

  juju bootstrap --constraints "tags=juju" --upload-tools --show-log --debug
  juju set-constraints "tags="
  juju add-machine --series xenial
  juju deploy --to lxc:1 local:xenial/ubuntu ubuntu

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