On Mon, Jan 27, 2020 at 05:07:06PM -0000, Colin Ian King wrote:
> I guess the next question is why dmidecode being run as root is required
> on a cloud init?
cloud-init uses DMI data to identify that it is running on certain
platforms. It will use /sys/class/dmi/... if available, but falls back
to dmidecode in its absence.
> What happens when arches don't have DMI data?
If running on a platform which identifies itself only via DMI data,
cloud-init will incorrectly determine that it is _not_ running on that
platform.
Given that other arches _can_ provide DMI data, and this cloud-init
behaviour is known, I would be surprised if any platform that _relies_
on it would launch a new architecture without DMI support. So if we get
no data (instead of a reboot), then I believe the current behaviour is
correct.
On Mon, Jan 27, 2020 at 05:07:06PM -0000, Colin Ian King wrote:
> I guess the next question is why dmidecode being run as root is required
> on a cloud init?
cloud-init uses DMI data to identify that it is running on certain
platforms. It will use /sys/class/dmi/... if available, but falls back
to dmidecode in its absence.
> What happens when arches don't have DMI data?
If running on a platform which identifies itself only via DMI data,
cloud-init will incorrectly determine that it is _not_ running on that
platform.
Given that other arches _can_ provide DMI data, and this cloud-init
behaviour is known, I would be surprised if any platform that _relies_
on it would launch a new architecture without DMI support. So if we get
no data (instead of a reboot), then I believe the current behaviour is
correct.