canonical / canonical/cloud-init
EC2 Metadata Service cloud-init warning on Packet.net bare-metal server
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 1.1k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 18
Description
This bug was originally filed in Launchpad as [LP: #1745920](https://bugs.launchpad.net/cloud-init/+bug/1745920)
Launchpad details
affected_projects = []
assignee = None
assignee_name = None
date_closed = None
date_created = 2018-01-29T05:35:16.376201+00:00
date_fix_committed = None
date_fix_released = None
id = 1745920
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1745920
milestone = None
owner = adam-elliot-fields
owner_name = Adam Fields
private = False
status = confirmed
submitter = adam-elliot-fields
submitter_name = Adam Fields
tags = ['dsid']
duplicates = []
_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.
Contributor guide
Assessment
This issue has not been assessed yet.