yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

** 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/1068801

Title:
  Metadata lazy loaded (even when disabled)

Status in Init scripts for use on cloud images:
  Fix Released

Bug description:
  A situation I was thinking probably is a bug.

  Looking at the boto fetching of metadata, they lazily load the
  dictionary that forms the instances metadata (and subsequent contained
  'sub' dictionaries as well). When the ec2 datasource is serialized it
  only contains whatever was loaded up to that point (depending on which
  fields were accessed). Now say the ec2 iptables rule is applied,
  further lazy loadings accessing contained sub entries of the metadata
  will fail loading. This would be counterintuitive to modules that
  expect fields to exist (and aren't prepared for lazy loading that
  happens in the lazy loading wrapper).

  Perhaps before serialization or in our custom ec2_utils (tbd) the full
  metadata could be traversed and stored so that this situation does not
  happen.

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