yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

** Also affects: cloud-init
   Importance: Undecided
       Status: New

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  cloud-init is disabled when data source is set to just "None"

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed

Bug description:
  For some images we build as part of the CPC programme, the target
  cloud doesn't support any sort of metadata, so they are configured
  with datasource_list as ["None"].

  However, we still want cloud-init to run because we lay down some
  configuration in /etc/cloud/cloud.cfg.d/* (to configure mirrors, for
  example).  Currently, ds-identify will disable cloud-init entirely,
  which is less than ideal.

  We either need another data-source name which means "None but please
  still run", or an independent way of telling ds-identify that its
  normal data-source logic doesn't work in this case (or just a way of
  overriding it).

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