Hello Geoff,

On Wed, Jun 6, 2018 at 9:14 PM,  <geoff.c...@beazley.com> wrote:
> I think that before a shutdown / restart the cloud-init configuration is 
> attached as there is /dev/sr1 visible. On shutdown / restart the config is no 
> longer attached and there is seemingly an error related to not being able to 
> find the data source: -
>
> 2018-06-06 15:15:11,297 - handlers.py[DEBUG]: finish: 
> init-network/search-NoCloudNet: SUCCESS: no network data found from 
> DataSourceNoCloudNet
> 2018-06-06 15:15:11,298 - util.py[WARNING]: No instance datasource found! 
> Likely bad things to come!
> 2018-06-06 15:15:11,298 - util.py[DEBUG]: No instance datasource found! 
> Likely bad things to come!
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/cloudinit/cmd/main.py", line 236, in 
> main_init
>     init.fetch(existing=existing)
>   File "/usr/lib/python2.7/site-packages/cloudinit/stages.py", line 343, in 
> fetch
>     return self._get_data_source(existing=existing)
>   File "/usr/lib/python2.7/site-packages/cloudinit/stages.py", line 253, in 
> _get_data_source
>     pkg_list, self.reporter)
>   File "/usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py", line 
> 320, in find_source
>     raise DataSourceNotFoundException(msg)
> DataSourceNotFoundException: Did not find any data source, searched classes: 
> (DataSourceNoCloudNet)
> 2018-06-06 15:15:11,302 - util.py[DEBUG]: Reading from 
> /sys/class/net/eth0/carrier (quiet=False)
> 2018-06-06 15:15:11,303 - util.py[DEBUG]: Read 2 bytes from 
> /sys/class/net/eth0/carrier
> 2018-06-06 15:15:11,303 - util.py[DEBUG]: Reading from 
> /sys/class/net/eth0/address (quiet=False)
> 2018-06-06 15:15:11,303 - util.py[DEBUG]: Read 18 bytes from 
> /sys/class/net/eth0/address
> 2018-06-06 15:15:11,303 - stages.py[DEBUG]: applying net config names for 
> {'version': 1, 'config': [{'subnets': [{'type': 'dhcp'}], 'type': 'physical', 
> 'name': 'eth0', 'mac_address': '00:1a:4a:16:01:05'}]}

I have the same issue since some months. Since cloud-init doesn't sees
any configuration, applies the default, which is to use dhcp.

I don't remember if it is a bug of cloud-init or a misconfiguration,
but now i solved removing cloud-init package after the first boot.

In case you want redeploying, you can keep cloud-init and disable its
work by disabling the service:

touch /etc/cloud/cloud-init.disabled

Luca

-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <lorenzetto.l...@gmail.com>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7BCX7R4XVUVLOWTKNC5HHUOCQ4NTAB2L/

Reply via email to