yahoo-eng-team team mailing list archive

[Ben Howard <ben.howard@xxxxxxxxxxxxx>]

** Changed in: cloud-init
       Status: Fix Committed => 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/1493453

Title:
  [SRU] vendor_data isn't parsed properly when using the nocloud
  datasource

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Trusty:
  Fix Released
Status in cloud-init source package in Vivid:
  Fix Released
Status in cloud-init source package in Wily:
  Fix Released

Bug description:
  SRU Justification:

  [IMPACT] The NoCloud Datasource assigns vendor_data to the wrong
  cloud-init internal variable. This causes the vendor_data to be
  improperly parsed, and prevents it from being consummed.

  [FIX] See original report below

  [TESTING]
  1. Start in-cloud instance
  2. Update cloud-init to version in proposed
  3. Populate /var/lib/cloud/seed/nocloud/{user,meta,vendor}-data:

    meta-data:
       instance-id: testing

    user-data:
       #cloud-config
       packages:
       - pastebinit

    vendor-data:
       #cloud-config
       runcmd:
       - [ "touch", "/tmp/vd-worked" ]

  3. Configure instance for NoCloud DS:

  $ cat > /etc/cloud/cloud.cfg.d/999-sru.cfg <<EOM
  DataSources: [ NoCloud }
  EOM

  4. Reboot
  5. Confirm that /tmp/vd-worked exists
  6. Confirm that pastebinit is installed

  [REGRESION POTENTIAL]
  Low. The NoCloud Datasource is used when there are no other datasources and is a local or fallback Datasource. This change only affects the vendor_data assignment which generally not used.

  [ORIGINAL REPORT]
  The following fix is needed:

  "self.vendordata = mydata['vendor-data']" must be changed to
  "self.vendordata_raw = mydata['vendor-data']"

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