no error message to console when cloud-config-url fails to load
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Medium
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
When booting an Ubuntu 12.04 ephmeral into MAAS commissioning on a
node which was unable to reach the region controller, I got the
following traceback:
| Can not apply stage final, no datasource found! Likely bad things to come!
| -------
| Traceback (most recent call last):
| File "/usr/bin/
| init.fetch()
| File "/usr/lib/
| return self._get_
| File "/usr/lib/
| pkg_list)
| File "/usr/lib/
| raise DataSourceNotFo
| DataSourceNotFo
| -------
Fuller log attached.
Changed in cloud-init (Ubuntu): | |
status: | Confirmed → Fix Released |
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: cloud-init. log shows:
2014-06-03 13:28:56,208 - util.py[WARNING]: No instance datasource found! Likely bad things to come!
the /var/log/
Jun 3 13:27:10 inst-trusty- 20140602- 191433 [CLOUDINIT] util.py[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/ stages. py", line 308, in fetch#012 return self._get_ data_source( )#012 File "/usr/lib/ python2. 7/dist- packages/ cloudinit/ stages. py", line 236, in _get_data_ source# 012 pkg_list)#012 File "/usr/lib/ python2. 7/dist- packages/ cloudinit/ sources/ __init_ _.py", line 260, in find_source#012 raise DataSourceNotFo undException( msg)#012DataSou rceNotFoundExce ption: Did not find any data source, searched classes: (DataSourceAzur eNet)
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.