Revision history [back]

Hello,

By default, cloudbase-init is set to try all the metadata providers. If a metadata provider is found, only that one will be used. In your case, it might have been the case the http provider was used, as it takes precedence over the configdrive one. Can you provide the cloudbase-init logs in order to check if the behaviour you got is the documented one?

Thank you,

Adrian Vladu