EC2 Metadata Service cloud-init warning on Packet.net bare-metal server

[Adam Fields]

This is most likely an issue with the cloud provider (Packet), but I'm filing the issue per the message:

**************************************************************************
# 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 #
# https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid #
# Make sure to include the cloud provider your instance is #
# running on. #
# #
# For more information see #
# https://bugs.launchpad.net/bugs/1660385 #
# #
# After you have filed a bug, you can disable this warning by #
# launching your instance with the cloud-config below, or #
# putting that content into #
# /etc/cloud/cloud.cfg.d/99-ec2-datasource.cfg #
# #
# #cloud-config #
# datasource: #
# Ec2: #
# strict_id: false #
**************************************************************************

Feel free to close as this isn't likely a bug with cloud-init itself.

[Scott Moser (smoser)]

Hi,
Thanks for taking the time to file a bug.

I'd like to get packet.net identified correctly.

Is there any way that we can do that?

[Adam Fields (adam-elliot-fields)]

Hey Scott,

What can I do to help? Do you need to be connected to somebody at Packet?

[Scott Moser (smoser)]

Adam,
Sorry for the slow reply.

Sure. Send an email to me (<email address hidden>).

I'd love to talk to someone. We can probably get something worked out.

Scott

[Simos Xenitellis  (simosx)]

Any updates on this one?

[Scott Moser (smoser)]

@Simos,
As for current status here, there is nothing that cloud-init can do to "detect"
that it is running on packet.net. At least not that I can see. As a work
around, you can run:
 dpkg-reconfigure cloud-init
then remove ec2 from the list, and :
  rm -Rf /var/lib/cloud/instance/warnings

If anyone from packet.io is listening, I'd love to get cloud-init working properly there, please reach out.

[Edward Vielmetti (edward-vielmetti)]

I am listening @smoser - drop me a note at <email address hidden> and I can help get this sorted out.

[Edward Vielmetti (edward-vielmetti)]

Our internal ticket on this issue says in part:

"To better support cloud-init (and probably other things) we need to include a unique identifier available within the OS for 3rd party software to use in order to recognize they are running on a Packet.net environment."

[Scott Moser (smoser)]

Just for reference for anyone reading along. I've had some email exchange with Ed and we are making progress on this. We'll probably end up with some sort of filesystem path that contains information indicatingi the system is running on packet.

its not the best, but in lieu of non-image based solutions this is what we can do.

[Darrel O'Pry (darrel.opry)]

would trying to query the metadata url work?

[Darrel O'Pry (darrel.opry)]

the metadata url for packet is https://metadata.packet.net/metadata

[Marques Johansson (marques)]

https://github.com/canonical/cloud-init/pull/680 is a PR that began work towards bringing Equinix Metal (formerly Packet) support to cloud-init. There is more discussion in that PR. Although it is currently closed by staleness, this work can be continued.

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3106