Data source = None error

[Guy]

My cloud provider is Linode (Akamai) https://www.linode.com/
While I have to particular issue, I get:

This message at login, asking me to report error:

Last login: Thu May 4 09:03:42 2023 from 104.158.25.145
**************************************************************************
# 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://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid #
# 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 #
**************************************************************************

[Scott Moser (smoser)]

hi, please run 'cloud-init collect-logs' and attach the cloud-init.tar.gz file to this bug.

After doing so, move the 'Status' of the bug back to 'New'.

Thanks.

[Guy (guydeschenes)]

As per email response request, here is the cloud-int.tar.gz output
Guy

[James Falcon (falcojr)]

Thanks for the logs. We've seen two of these bugs recently, so it looks like something has changed over at Akamai such that cloud-init is no longer detecting the datasource correctly. This is likely something that will need to be fixed on their end, or they'll need to provide what should change in cloud-init. I'm going to set this to incomplete until we can figure out what needs to change.

[James Falcon (falcojr)]

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

[Chad Smith (chad.smith)]

Hi @Guy,
 There are a couple of updates and questions related to this failure path and whether or not this behavior is a regression from previous image launched on Linode. If you have a chance and can respond to the Github issue, I think we may have some headway here with a couple of Linode representatives https://github.com/canonical/cloud-init/issues/4107#issuecomment-1548233391.