Vultr VPS - EC2 Metadata Service; does not appear to be running on Amazon EC2

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1901458

Launchpad details

affected_projects = []
assignee = None
assignee_name = None
date_closed = 2020-10-26T19:35:00.068089+00:00
date_created = 2020-10-26T01:32:39.242409+00:00
date_fix_committed = None
date_fix_released = None
id = 1901458
importance = medium
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1901458
milestone = None
owner = iainsgillis
owner_name = Iain Gillis
private = False
status = wont_fix
submitter = iainsgillis
submitter_name = Iain Gillis
tags = ['dsid']
duplicates = []

Launchpad user Iain Gillis(iainsgillis) wrote on 2020-10-26T01:32:39.242409+00:00

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.

[ubuntu-server-builder]

Launchpad user Iain Gillis(iainsgillis) wrote on 2020-10-26T01:32:39.242409+00:00

[ubuntu-server-builder]

Launchpad user Iain Gillis(iainsgillis) wrote on 2020-10-26T01:34:28.209323+00:00

Apologies -- uploaded the incorrect attachment with original submission
Launchpad attachments: cloud-init.tar.gz

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2020-10-26T13:43:54.366731+00:00

@lain, thanks for taking the time to file this bug.

from the collected ds-identify.log file we have

DMI_PRODUCT_NAME=VC2
DMI_SYS_VENDOR=Vultr

Assuming Vultr puts this DMI_SYS_VENDOR in reliably , then we can use this to
identify Vultr and squelch the warning.

Alternatively, we could add a vultr specific datasource. At first read, it
appears that vultr runs a ec2 lookalike service, but also has its own native
metadata service with 'v1' in the path..

Further reading:

https://www.vultr.com/metadata/
https://www.vultr.com/api/#server_create
https://www.vultr.com/docs/getting-started-with-cloud-init
https://discuss.vultr.com/discussion/2132/how-to-access-userdata

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2020-10-26T14:29:29.596859+00:00

#628

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2020-10-26T19:34:41.425990+00:00

Well, this was good. To recap:

1. I put up a pull request to support Vultr as a "known" EC2 clone.
   Add support to EC2 for identifying Vultr cloud. #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.

[ubuntu-server-builder]

Launchpad user Richard Harding(rharding) wrote on 2020-10-26T19:47:53+00:00

Thank you for the help in driving that through and we'll look forward to
the Vultr contribution to upstream!

On Mon, Oct 26, 2020 at 3:40 PM Scott Moser 1901458@bugs.launchpad.net
wrote:

Well, this was good. To recap:

1. I put up a pull request to support Vultr as a "known" EC2 clone.
   Add support to EC2 for identifying Vultr cloud. #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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1901458/+subscriptions

[ubuntu-server-builder]

Launchpad user Iain Gillis(iainsgillis) wrote on 2020-10-26T20:04:28+00:00

Thanks, folks. Really appreciate your work.

Sorry I don’t have more technical chops to contribute more directly.

Much obliged,
Iain

On Mon, Oct 26, 2020, at 13:47, Richard Harding wrote:

Thank you for the help in driving that through and we'll look forward to
the Vultr contribution to upstream!

On Mon, Oct 26, 2020 at 3:40 PM Scott Moser 1901458@bugs.launchpad.net
wrote:

Well, this was good. To recap:

1. I put up a pull request to support Vultr as a "known" EC2 clone.
   Add support to EC2 for identifying Vultr cloud. #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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1901458/+subscriptions

--
You received this bug notification because you are subscribed to the bug
report.
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