yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #92314
[Bug 2006518] Re: Inconsistent kernel command line datasource detection
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/4075
** Bug watch added: github.com/canonical/cloud-init/issues #4075
https://github.com/canonical/cloud-init/issues/4075
** Changed in: cloud-init
Status: Triaged => 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/2006518
Title:
Inconsistent kernel command line datasource detection
Status in cloud-init:
Expired
Bug description:
cloud-init has undocumented support for declaring datasources using
the kernel commandline. This proves valuable in edge case scenarios as
a workaround when ds-identify detection is broken.
This behavior is inconsistently supported across datasources, several
of which[1] do some form of runtime detection in the datasource module
which may override cmdline-specified datasources.
We should either fix current behavior or provide a new key name in the
cmdline that always overrides runtime cloud-init detection in all
datasources (likely involving a refactor into the datasource class).
Once complete, this should be documented.
Originally reported in [2].
[1] one example: https://github.com/canonical/cloud-init/blob/02202954c65a7a1cdb9b28703bd0af01edd0e091/cloudinit/sources/DataSourceOpenStack.py#L271
[2] https://bugs.launchpad.net/cloud-init/+bug/1815990
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2006518/+subscriptions
References