yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #84814
[Bug 1901831] Re: A new feature in cloud-init identified possible datasources for this system as: [] However, the datasource used was: None
[Expired for cloud-init because there has been no activity for 60 days.]
** Changed in: cloud-init
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1901831
Title:
A new feature in cloud-init identified possible datasources for this
system as: [] However, the datasource used was: None
Status in cloud-init:
Expired
Bug description:
Using: Ubuntu 20.04
**************************************************************************
# 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 #
**************************************************************************
This worked fine in other CentOS 7 machines, but now cloud-init takes
a lot of time to deploy because it tries to fetch the config details
from other data sources.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1901831/+subscriptions
References