On Tue, Oct 27, 2020 at 04:54:13PM +0100, Thomas Goirand wrote:
> Testing to start the OpenStack image (well, the "genericcloud" image), I
> couldn't login into it, because there isn't any metadata service configured
> in it.
This is incorrect. The package uses
/lib/systemd/system-generators/cloud-init-generator to generate a
config. This works in general:
| $ cat /run/cloud-init/cloud.cfg
| datasource_list: [ Azure, None ]
So, please provide more information.
> After that, it appears that /etc/hosts wasn't configued at all with the
> hostname, therefore, the hostname couldn't be resolved even within the VM
> itself. I'm not sure if this is related or not, however.
Show logs? /run/cloud-init/cloud-init-generator.log for example.
> IMO, this is of severity grave, because the image is not usable without a
> tweak (ie: impossible to login).
Severities have no real meaning for non-package resources. And the same
mechanism clearly works on Azure and EC2 without problems, so it would
be only "important".
Bastian
--
No one wants war.
-- Kirk, "Errand of Mercy", stardate 3201.7
