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

This bug was originally filed in Launchpad as [LP: #1769690](https://bugs.launchpad.net/cloud-init/+bug/1769690)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2018-05-07T15:40:34.448074+00:00

date_fix_committed = None

date_fix_released = None

id = 1769690

importance = low

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1769690

milestone = None

owner = chad.smith

owner_name = Chad Smith

private = False

status = confirmed

submitter = chad.smith

submitter_name = Chad Smith

tags = []

duplicates = []

_Launchpad user **Chad Smith(chad.smith)** wrote on 2018-05-07T15:40:34.448074+00:00_

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