@Jesse thanks for the bump and notes on this bug, since the origin of this bug we had added a related feature which allows init-lovel based datasources to set the hostname before network is brought online[1]. From my recollection of the feature, it requires that the datasource meta-data.local-hostname[2] (not user-data.hostname) to provide "local-hostname" config.
If you get a chance would you be able to:
1. provide the steps used in terraform to reproduce this issue
2. attach the tar.gz from cloud-init `sudo collect-logs -u`. Note that this collect-logs will include user-data, so please double check to make sure you don't have sensitive information (passwords/credentials) provided from the user-data/meta-data provided during launch.
Thank you, the attached logs will help confirm suspicions on why this feature isn't quite enough for terraform type deployments.
@Jesse thanks for the bump and notes on this bug, since the origin of this bug we had added a related feature which allows init-lovel based datasources to set the hostname before network is brought online[1]. From my recollection of the feature, it requires that the datasource meta-data. local-hostname[ 2] (not user-data.hostname) to provide "local-hostname" config.
If you get a chance would you be able to: credentials) provided from the user-data/meta-data provided during launch.
1. provide the steps used in terraform to reproduce this issue
2. attach the tar.gz from cloud-init `sudo collect-logs -u`. Note that this collect-logs will include user-data, so please double check to make sure you don't have sensitive information (passwords/
Thank you, the attached logs will help confirm suspicions on why this feature isn't quite enough for terraform type deployments.
References:
[1] https:/ /github. com/canonical/ cloud-init/ commit/ 133ad2cb327ad17 b7b81319fac8f9f 14577c04df /github. com/canonical/ cloud-init/ blob/main/ cloudinit/ sources/ __init_ _.py#L754
[2] https:/