yahoo-eng-team team mailing list archive

[Robert Schweikert <1883907@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When creating an AMI from a running instance without cleaning the cloud-
init cache an instance from the new AMI is no properly identified as a
new instance and none of the PER_INSTANCE tasks will be executed.

The problem is that the Ec2 data source will return the cached instance-
id rather than the new instance ID.

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
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/1883907

Title:
  EC2 data source does not properly return the instance ID when cached
  data exists

Status in cloud-init:
  New

Bug description:
  When creating an AMI from a running instance without cleaning the
  cloud-init cache an instance from the new AMI is no properly
  identified as a new instance and none of the PER_INSTANCE tasks will
  be executed.

  The problem is that the Ec2 data source will return the cached
  instance-id rather than the new instance ID.

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