Well, this was good. To recap:
1. I put up a pull request to support Vultr as a "known" EC2 clone. https://github.com/canonical/cloud-init/pull/628 2. github users eb3095 (https://github.com/eb3095) and ddymko (https://github.com/ddymko) are associated with Vultr and are expecting to contribute a native cloud-init soon. 3. I closed PR 628 to not add confusion. 4. I'm closing this issue. ** Changed in: cloud-init Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1901458 Title: Vultr VPS - EC2 Metadata Service; does not appear to be running on Amazon EC2 Status in cloud-init: Won't Fix Bug description: The message when I login to a VPS instance cloned from a previous system image: This system is using the EC2 Metadata Service, but does not appear to be running on Amazon EC2 or one of cloud-init's known platforms that provide a EC2 Metadata service. In the future, cloud-init may stop reading metadata from the EC2 Metadata Service unless the platform can be identified. If you are seeing this message, please file a bug against cloud-init at [url]. Make sure to include the cloud provider your instance is running on. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1901458/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
