Comment 6 for bug 1788487

Revision history for this message
Ben Raymond (benray12) wrote :

I appear to be running into the same issue described by Mark. Platform is OpenStack using VMware (VC + ESXi). I first noticed this after upgrading a template from Ubuntu 16.04.2 to 16.04.5 which bumped cloud-init from 17.2-35 to 18.4-0. I got the EC2 warning as well :)

I'll be happy to check the explicit option if that currently works. I did try with only three (including ConfigDrive in case we wanted to mount an ISO on occasion) but that did not work.

If https://bugs.launchpad.net/cloud-init/+bug/1669875 is fixed would cloud-init be able to identify VMware instance and avoid explicit datasource?

thanks!
Ben