yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #67893
[Bug 1674128] Re: Unable to identify CloudStack platform correctly
This is believed to be fixed in 17.1.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1674128
Title:
Unable to identify CloudStack platform correctly
Status in cloud-init:
Fix Released
Bug description:
Hey!
With the latest CloudInit on Xenial, I got:
```
**************************************************************************
# A new feature in cloud-init identified possible datasources for #
# this system as: #
# ['Ec2', 'None'] #
# However, the datasource used was: CloudStack #
# #
# 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 #
**************************************************************************
```
In the source code, I see the detection script is looking for
"CloudStack" in DMI. It doesn't find it as it doesn't exist.
CloudStack runs on a variety of hypervisor. We run it on top of
QEMU/KVM. I don't think there is an easy way to find out we are
running CloudStack without contacting the metadata server.
```
/sys/class/dmi/id/product_name:Standard PC (i440FX + PIIX, 1996)
```
I would suggest to not display a warning when `datasource_list` is set
to a unique value, since in this case, there is nothing to try and
it's likely the unique value is the correct one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1674128/+subscriptions
References