canonical / cloud-init

Official upstream for the cloud-init: cloud instance initialization
https://cloud-init.io/
Other
2.99k stars 883 forks source link

Getting Datasource as None on "VMware Photon OS 5.0" #5630

Open mdshoaib707 opened 2 months ago

mdshoaib707 commented 2 months ago

Bug report

getting the error when I run /usr/bin/cloud-init init on the "VMware Photon OS 5.0"


A new feature in cloud-init identified possible datasources for
this system as:
[]
However, the datasource used was: None

In the future, cloud-init will only attempt to use datasources that
are identified or specifically configured.
For more information see
https://bugs.launchpad.net/bugs/1669675

If you are seeing this message, please file a bug against
cloud-init at
https://github.com/canonical/cloud-init/issues
Make sure to include the cloud provider your instance is
running on.

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-warnings.cfg

cloud-config

warnings:
dsid_missing_source: off


Steps to reproduce the problem

Run the command /usr/bin/cloud-init init and then we get the above error.

Environment details

cloud-init logs

A new feature in cloud-init identified possible datasources for
this system as:
[]
However, the datasource used was: None

In the future, cloud-init will only attempt to use datasources that
are identified or specifically configured.
For more information see
https://bugs.launchpad.net/bugs/1669675

If you are seeing this message, please file a bug against
cloud-init at
https://github.com/canonical/cloud-init/issues
Make sure to include the cloud provider your instance is
running on.

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-warnings.cfg

cloud-config

warnings:
dsid_missing_source: off


aciba90 commented 2 months ago

Thanks for reporting this issue.

To better understand what the issue is, could you please attach the cloud-init logs? Run cloud-init collect-logs in the instance and paste the tarball in this issue

I mark this issue as incomplete until then.