yahoo-eng-team team mailing list archive

[Dan Watkins <1880701@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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": []
 }
}

** Affects: cloud-init
     Importance: Undecided
         Status: New

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

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

Status in cloud-init:
  New

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": []
   }
  }

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