<div dir="auto">Thanks Michael.<div dir="auto">I have just tried to use dpkg to reconfigure cloud init source forcing ConfigDrive it did not solve. I am going to force it with with diskimage builder. </div><div dir="auto">I hope this will work.</div><div dir="auto">Ignazio</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il Ven 14 Feb 2020, 22:57 Michael Johnson <<a href="mailto:johnsomor@gmail.com">johnsomor@gmail.com</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I haven't had time to look at your logs, but I can tell you that<br>
configdrive has worked in the Ubuntu images since at least Xenial (I<br>
am pretty sure trusty, but I can't remember for sure).<br>
The Octavia project uses it exclusively for the amphora instances.<br>
<br>
I'm not sure where you got your image, but there is a setting for<br>
cloud-init that defines which data sources it will use. For Octavia we<br>
explicitly set this in our images to only poll configdrive to speed<br>
the boot process.<br>
<br>
We build our images using diskimage-builder, and this element (script)<br>
is the component we use to set the cloud-init datasource:<br>
<br>
<a href="https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/cloud-init-datasources/install.d/05-set-cloud-init-sources" rel="noreferrer noreferrer" target="_blank">https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/cloud-init-datasources/install.d/05-set-cloud-init-sources</a><br>
<br>
Maybe check the settings for cloud-init inside your image by grep for<br>
"datasource_list" in /etc/cloud/cloud.cfg.d/* ?<br>
<br>
Michael<br>
<br>
On Fri, Feb 14, 2020 at 11:29 AM Ignazio Cassano<br>
<<a href="mailto:ignaziocassano@gmail.com" target="_blank" rel="noreferrer">ignaziocassano@gmail.com</a>> wrote:<br>
><br>
> Hello, at the following link you can find the cloud init logs file:<br>
><br>
> <a href="https://drive.google.com/open?id=1IXp85kfLAC4H3Jp2pHrkwij61XWiFNva" rel="noreferrer noreferrer" target="_blank">https://drive.google.com/open?id=1IXp85kfLAC4H3Jp2pHrkwij61XWiFNva</a><br>
><br>
> PS<br>
> I can mount and read metadata mount manually the cdrom and I do not understand why cloud-init cannot.<br>
> Ignazio<br>
><br>
> Il giorno ven 14 feb 2020 alle ore 20:14 Ignazio Cassano <<a href="mailto:ignaziocassano@gmail.com" target="_blank" rel="noreferrer">ignaziocassano@gmail.com</a>> ha scritto:<br>
>><br>
>> Hello, attaced here thera are the cloud-init logs form ubuntu 18 instance.<br>
>> Note I can mount /dev/cdrom and see metadata:<br>
>> mount -o ro /dev/cdrom /mnt<br>
>> ls -laR /mnt<br>
>> total 10<br>
>> dr-xr-xr-x 4 root root 2048 Feb 14 17:05 .<br>
>> drwxr-xr-x 24 root root 4096 Feb 14 17:08 ..<br>
>> dr-xr-xr-x 4 root root 2048 Feb 14 17:05 ec2<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 openstack<br>
>><br>
>> /mnt/ec2:<br>
>> total 8<br>
>> dr-xr-xr-x 4 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 4 root root 2048 Feb 14 17:05 ..<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2009-04-04<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 latest<br>
>><br>
>> /mnt/ec2/2009-04-04:<br>
>> total 5<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 4 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 963 Feb 14 17:05 meta-data.json<br>
>><br>
>> /mnt/ec2/latest:<br>
>> total 5<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 4 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 963 Feb 14 17:05 meta-data.json<br>
>><br>
>> /mnt/openstack:<br>
>> total 22<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 4 root root 2048 Feb 14 17:05 ..<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2012-08-10<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2013-04-04<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2013-10-17<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2015-10-15<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2016-06-30<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2016-10-06<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2017-02-22<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 2018-08-27<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 latest<br>
>><br>
>> /mnt/openstack/2012-08-10:<br>
>> total 6<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1056 Feb 14 17:05 meta_data.json<br>
>><br>
>> /mnt/openstack/2013-04-04:<br>
>> total 6<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1759 Feb 14 17:05 meta_data.json<br>
>><br>
>> /mnt/openstack/2013-10-17:<br>
>> total 7<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1759 Feb 14 17:05 meta_data.json<br>
>> -r--r--r-- 1 root root 2 Feb 14 17:05 vendor_data.json<br>
>><br>
>> /mnt/openstack/2015-10-15:<br>
>> total 7<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1809 Feb 14 17:05 meta_data.json<br>
>> -r--r--r-- 1 root root 397 Feb 14 17:05 network_data.json<br>
>> -r--r--r-- 1 root root 2 Feb 14 17:05 vendor_data.json<br>
>><br>
>> /mnt/openstack/2016-06-30:<br>
>> total 7<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1824 Feb 14 17:05 meta_data.json<br>
>> -r--r--r-- 1 root root 397 Feb 14 17:05 network_data.json<br>
>> -r--r--r-- 1 root root 2 Feb 14 17:05 vendor_data.json<br>
>><br>
>> /mnt/openstack/2016-10-06:<br>
>> total 8<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1824 Feb 14 17:05 meta_data.json<br>
>> -r--r--r-- 1 root root 397 Feb 14 17:05 network_data.json<br>
>> -r--r--r-- 1 root root 2 Feb 14 17:05 vendor_data.json<br>
>> -r--r--r-- 1 root root 14 Feb 14 17:05 vendor_data2.json<br>
>><br>
>> /mnt/openstack/2017-02-22:<br>
>> total 8<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1824 Feb 14 17:05 meta_data.json<br>
>> -r--r--r-- 1 root root 397 Feb 14 17:05 network_data.json<br>
>> -r--r--r-- 1 root root 2 Feb 14 17:05 vendor_data.json<br>
>> -r--r--r-- 1 root root 14 Feb 14 17:05 vendor_data2.json<br>
>><br>
>> /mnt/openstack/2018-08-27:<br>
>> total 8<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1824 Feb 14 17:05 meta_data.json<br>
>> -r--r--r-- 1 root root 397 Feb 14 17:05 network_data.json<br>
>> -r--r--r-- 1 root root 2 Feb 14 17:05 vendor_data.json<br>
>> -r--r--r-- 1 root root 14 Feb 14 17:05 vendor_data2.json<br>
>><br>
>> /mnt/openstack/latest:<br>
>> total 8<br>
>> dr-xr-xr-x 2 root root 2048 Feb 14 17:05 .<br>
>> dr-xr-xr-x 11 root root 2048 Feb 14 17:05 ..<br>
>> -r--r--r-- 1 root root 1824 Feb 14 17:05 meta_data.json<br>
>> -r--r--r-- 1 root root 397 Feb 14 17:05 network_data.json<br>
>> -r--r--r-- 1 root root 2 Feb 14 17:05 vendor_data.json<br>
>> -r--r--r-- 1 root root 14 Feb 14 17:05 vendor_data2.json<br>
>><br>
>> Thanks<br>
>> Ignazio<br>
>><br>
>> Il giorno ven 14 feb 2020 alle ore 19:16 Jeremy Stanley <<a href="mailto:fungi@yuggoth.org" target="_blank" rel="noreferrer">fungi@yuggoth.org</a>> ha scritto:<br>
>>><br>
>>> On 2020-02-14 17:51:01 +0100 (+0100), Ignazio Cassano wrote:<br>
>>> > Hello, I configured config drive and centos instances works fine<br>
>>> > with it. Ubuntu bionic tries to get metadata from network and<br>
>>> > cloud-init does not set hostname and does not insert keys for ssh.<br>
>>><br>
>>> The cloud-init changelog indicates that initial support for<br>
>>> configdrive first appeared in 0.6.3, so the versions in Ubuntu<br>
>>> Bionic (and even Xenial) should be new enough to make use of it. In<br>
>>> fact, the official Ubuntu bionic-updates package suite includes<br>
>>> cloud-init 19.4 (the most recent release), so missing<br>
>>> features/support seem unlikely. Detailed log entries from cloud-init<br>
>>> running at boot might help in diagnosing the problem.<br>
>>> --<br>
>>> Jeremy Stanley<br>
</blockquote></div>