datasource problem after upgrade

[jperon]

Bug report

Just filing this one as requested by the message itself. Here is what I get after upgrading my Debian vps on PulseHeberg:

**************************************************************************
# A new feature in cloud-init identified possible datasources for        #
# this system as:                                                        #
#   []                                                                   #
# However, the datasource used was: NoCloud                              #
#                                                                        #
# 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

Just log into the system, for example with ssh.

Environment details

• Cloud-init version: 24.3.1-2 (as reported by apt policy cloud-init)
• Operating System Distribution: Debian sid
• Cloud provider, platform or installer type: PulseHeberg

cloud-init logs

Doesn’t seem relevant here? cloud-init.log

[aciba90]

Hi @jperon, thanks for reporting. Could you please attach the logs?

This sounds very likely a consequence of some of the changes on platform identification in cloud-init. If you are sure that NoCloud is the datasource needed here and if /etc/cloud/cloud.cfg does not contain a datasource_list key with NoCloud, then I think one way to fix this would be adding to /etc/cloud/cloud.cfg:

datasource_list: [NoCloud]

[jperon]

@aciba90 Thanks for your attention. I added the log to first post. I don’t know which datasource is needed: I think it’s part of the VPS hosting provisionning, as I didn’t install cloud-init myself. But adding the line datasource_list: [NoCloud] didn’t fix the problem (even after reboot).

[aciba90]

How about?

datasource_list: [NoCloud, None]

[jperon]

No, still same message.

[holmanb]

@jperon please follow this guide so that this issue can be resolved.