cloud-init

`cloud-init query` cannot be used to determine the current datasource

Bug #1880701 reported by Dan Watkins on 2020-05-26

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	cloud-init	Fix Released	Medium	Unassigned

Bug Description

On a lxd container, which uses the NoCloud datasource[0], the only place where "NoCloud" is queryable is in `datasource_list`:

# cloud-init query -a | grep -B1 -A2 NoCloud
  "datasource_list": [
   "NoCloud",
   "None"
  ],

With ds-identify enabled, you probably _can_ take that first value as the correct DS (because if that DS wasn't used then you probably don't have access to the instance), but that won't generalise well. We should provide the name of the datasource used in the queryable data somewhere.

[0] # cat /run/cloud-init/result.json
{
"v1": {
"datasource": "DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]",
"errors": []
}
}