-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EC2 Metadata Service cloud-init warning on Packet.net bare-metal server #3106
Comments
Launchpad user Scott Moser(smoser) wrote on 2018-02-05T21:45:12.944896+00:00 Hi, I'd like to get packet.net identified correctly. Is there any way that we can do that? |
Launchpad user Adam Fields(adam-elliot-fields) wrote on 2018-02-05T22:00:43.845609+00:00 Hey Scott, What can I do to help? Do you need to be connected to somebody at Packet? |
Launchpad user Scott Moser(smoser) wrote on 2018-02-28T02:48:42.537587+00:00 Adam, Sure. Send an email to me (scott.moser@canonical.com). I'd love to talk to someone. We can probably get something worked out. Scott |
Launchpad user Scott Moser(smoser) wrote on 2018-03-01T16:32:24.558505+00:00 Launchpad attachments: debug info collected from a packet.net system |
Launchpad user Simos Xenitellis (simosx) wrote on 2018-07-09T11:34:40.231488+00:00 Any updates on this one? |
Launchpad user Scott Moser(smoser) wrote on 2018-07-09T15:22:28.588922+00:00 @simos, If anyone from packet.io is listening, I'd love to get cloud-init working properly there, please reach out. |
Launchpad user Edward Vielmetti(edward-vielmetti) wrote on 2018-11-30T14:52:41.117413+00:00 I am listening @smoser - drop me a note at ed@packet.com and I can help get this sorted out. |
Launchpad user Edward Vielmetti(edward-vielmetti) wrote on 2018-11-30T15:56:57.067978+00:00 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." |
Launchpad user Scott Moser(smoser) wrote on 2018-12-04T16:04:16.740005+00:00 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. |
Launchpad user Darrel O'Pry(darrel.opry) wrote on 2019-02-08T02:09:19.473855+00:00 would trying to query the metadata url work? |
Launchpad user Darrel O'Pry(darrel.opry) wrote on 2019-02-08T02:13:36.026558+00:00 the metadata url for packet is https://metadata.packet.net/metadata |
Launchpad user Marques Johansson(marques) wrote on 2021-06-02T16:52:23.893456+00:00 #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. |
This bug was originally filed in Launchpad as LP: #1745920
Launchpad details
Launchpad user Adam Fields(adam-elliot-fields) wrote on 2018-01-29T05:35:16.376201+00:00
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.
The text was updated successfully, but these errors were encountered: