datasource missing in LXD in OpenStack which created by conjure-up

Bug #1674099 reported by BlueT - Matthew Lien - 練喆明
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
New
Undecided
Unassigned

Bug Description

I created a m1.tiny VM instance with xenial-lxd image.
Once login, it shows this warning.

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

Disable the warnings above by:
  touch /home/ubuntu/.cloud-warnings.skip
or
  touch /var/lib/cloud/instance/warnings/.skip
ubuntu@tt2:~$

I setup the new host server with conjure-up OpenStack single-host (NovaLXD), use default configuration.

root@con-up:/etc/apt# snap list conjure-up
Name Version Rev Developer Notes
conjure-up 2.1.2 133 canonical classic

root@con-up:/etc/apt# dpkg -la|grep lxd
ii lxd 2.11-0ubuntu4~ubuntu16.04.1~ppa1 amd64 Container hypervisor based on LXC - daemon
ii lxd-client 2.11-0ubuntu4~ubuntu16.04.1~ppa1 amd64 Container hypervisor based on LXC - client

Tags: dsid
Revision history for this message
Scott Moser (smoser) wrote :

Thank you for taking the time to file this bug.
nova-lxd changes are being tracked under bug 1661797.
Please follow that bug for updates.

Scott

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.