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

Bug #1769690 reported by Chad Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Expired
Low
Unassigned

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

Revision history for this message
Chad Smith (chad.smith) wrote :
description: updated
Changed in cloud-init:
importance: Undecided → Low
Revision history for this message
James Falcon (falcojr) wrote :
Changed in cloud-init:
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.