cloud-init team mailing list archive

[Laurent Dumont <laurentfdumont@xxxxxxxxx>]

Thanks James

For the overall delay, this is expected since we might deploy the instance
in a Openstack env/network that is degraded.

The metadata server might not answer but we still want the VM to be usable
through the console/serial.

I'll take a look at the Openstack data source.

Laurent

On Mon, May 16, 2022, 8:14 AM James Falcon <james.falcon@xxxxxxxxxxxxx>
wrote:

> Timeouts that long usually indicate that your instances are misidentifying
> a datasource and trying to connect to it. Check the last few lines of
> /run/cloud/ds-identify.log and ensure the datasource detected is what
> you're expecting. If not, ideally that would be fixed in your image/cloud
> setup, but you can also manually specify the datasource(s) to use/detect in
> /etc/cloud.cfg or /etc/cloud.cfg.d. For example, to specify using only
> Openstack, you could write
>
> datasource_list: [ Openstack ]
>
> to /etc/cloud/cloud.cfg.d/99_datasource.cfg. Note that if a single
> datasource is specified, cloud-init will automatically use it. If more than
> one is specified, cloud-init (via an early boot script called ds-identify)
> will check to see which datasource it should be using. If no
> suitable datasource can be found, cloud-init will be disabled.
>
> If that's not helping, Openstack timeouts can also be configured in
> /etc/cloud/cloud.cfg[.d]. The details can be found here:
>
> https://cloudinit.readthedocs.io/en/latest/topics/datasources/openstack.html#configuration
>
> Hope that helps!
>
> Thanks,
> James
>
> On Sat, May 14, 2022 at 3:33 PM Laurent Dumont <laurentfdumont@xxxxxxxxx>
> wrote:
>
>> Hey folks,
>> I am building a small custom image based on 22.04. Its primary use is to
>> be deployed to troubleshoot network/strange things in Openstack.
>>
>> We are usually expecting cloud-init to work with the OpenstackDatasource
>> or the LocalDatasource (config drive) and it works great!
>>
>> But there are some cases where I know we won't be able to reach
>> cloudinit/some weird issue with the configdrive CDROM drive with cloud-init.
>>
>> With a stock cloud-init and a setup where there is no working Datasource,
>> I see that the overall boot time is around 400+ seconds.
>>
>> Is there a way to configure global timeout so that
>>
>>    - If the URL metadata server doesn't respond.
>>    - If the config-drive is not mounted/not working.
>>    - Skip the rest of the initialization?
>>
>> Maybe a middle ground where it can at least try to get the interfaces up?
>>
>> Thanks!
>>
>>
>> --
>> Mailing list: https://launchpad.net/~cloud-init
>> Post to     : cloud-init@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~cloud-init
>> More help   : https://help.launchpad.net/ListHelp
>>
>