On Wed, Apr 03, 2019 at 08:54:58AM +0000, Kenn Leth Hansen wrote:
> I've discovered the CloudStack datasource causes cloud-init to wait for 120
> seconds before continuing to the next datasource if no service is responding
> on port 80 on the DHCP server address. As I am using an Ec2-style metadata
> server, I need to wait 120 seconds every time i boot an instance until it is
> operational as this listens on "magic" IP 169.254.169.254 and I cannot easily
> redirect traffic to this IP.
> Would it be possible to move the Ec2 datasource up the list like "[ NoCloud,
> AltCloud, ConfigDrive, OpenStack, Ec2, CloudStack, ${DIGITAL_OCEAN_SOURCE}
> MAAS, OVF, GCE, None ]"? This also seems to be in line with expectations on
> how the datasources have been sorted before dc1abbe1.
The data-source override is mostly gone from new images. The cloud-init
from Buster does even more auto-detection for supported stuff. Please
test this version.
Regards,
Bastian
--
Phasers locked on target, Captain.
