[ovirt-users] Re: cloud-init behaviour after reboot and growpart

Hi all, After having successfully run cloud-init with the "initial run" box checked, I meet an issue after rebooting the el7 vm. At the boot time, cloud-init waits for a data source that doesn't exist anymore and I have to wait serveral timeouts like this one: open 'http://169.254.169.254/openstack' with {'url': 'http://169.254.169.254/openstack', 'headers': {'User-Agent': 'Cloud-Init/0.7.9'}, 'allow_redirects': True, 'method': 'GET', 'timeout': 10.0} configuration As a workaround,  I must include in the initial custom script "touch /etc/cloud/cloud-init.disabled" so as to the vm to boot properly. Now I'd like cloud-init not to be fully disabled because I need it resizes the filesystem after the growpart step. Can anyone help me with this?