canonical / canonical/cloud-init
datasource problem after upgrade
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 1.1k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 18
Description
# 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](https://pulseheberg.com/)
## cloud-init logs
Doesn’t seem relevant here?
[cloud-init.log](https://github.com/user-attachments/files/17961833/cloud-init.log)
Contributor guide
Assessment
This issue has not been assessed yet.