Comment 2 for bug 1303934

I have to mark this as fix-released. I'm not really sure how you could have seen the output you saw, and I just verified that cloud-init in trusty gives a saner message. Heres how:
 sudo dpkg-reconfigure cloud-init # select 'Azure' on an openstack instance, something that iwll not be found
 sudo cloud-init init --local
 sudo cloud-init init

this shows on stderr:
 2014-06-03 13:28:56,208 -[WARNING]: No instance datasource found! Likely bad things to come!
the /var/log/cloud-init.log shows:

Jun 3 13:27:10 inst-trusty-20140602-191433 [CLOUDINIT][DEBUG]: No instance datasource found! Likely bad things to come!#012Traceback (most recent call last):#012 File "/usr/bin/cloud-init", line 242, in main_init#012 init.fetch()#012 File "/usr/lib/python2.7/dist-packages/cloudinit/", line 308, in fetch#012 return self._get_data_source()#012 File "/usr/lib/python2.7/dist-packages/cloudinit/", line 236, in _get_data_source#012 pkg_list)#012 File "/usr/lib/python2.7/dist-packages/cloudinit/sources/", line 260, in find_source#012 raise DataSourceNotFoundException(msg)#012DataSourceNotFoundException: Did not find any data source, searched classes: (DataSourceAzureNet)

See here, the 'searched classes' is not empty.

The other part of this bug (what I actually think happened) is that cloud-init did not sanely warn that it tried to read something from the cloud_config_url and was unable to get it.

I'm just going to re-purpose this bug to that.