yahoo-eng-team team mailing list archive

[James Falcon <1769690@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3171

** Bug watch added: github.com/canonical/cloud-init/issues #3171
   https://github.com/canonical/cloud-init/issues/3171

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

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

Title:
  IBMCloud ds-identify detects NoCloud but cloud-init determines
  ConfigDrive

Status in cloud-init:
  Expired

Bug description:
  cloud-init: 18.2-4-g05926e48-0ubuntu1~16.04.2

  Xenial IBMCloud template-based instances (with user-data) raise a ds-
  identify warning banner although ConfigDrive is properly detected:

  ...
  # A new feature in cloud-init identified possible datasources for        #
  # this system as:                                                        #
  #   ['NoCloud', 'None']                                                  #
  # However, the datasource used was: ConfigDrive
  ...

  Xenial IBMCloud instances mount a METADATA drive to
  /var/lib/cloud/seed/config_drive which cloud-init can detect and
  process properly as a ConfigDrive datasource. But, at the time ds-
  identify runs, it doesn't yet see that mount and as a result only
  detects NoCloud datasource.

  from /etc/fstab
  LABEL=METADATA /var/lib/cloud/seed/config_drive vfat defaults,nofail 0 0

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