As requested by customer in support case, I replicate this upstream bug to RHBZ.
Description of problem:
CentOS 7.4 builds on Cloudstack 4.8 don't run cloud-init because the newer version of cloud-init doesn't appear to like the way the dhclient lease file is named.
I've just built a CentOS 7.4 instance in one of my CloudStack 4.8 clusters. Unfortunately, cloud-init fails with the following in snippet in /var/log/cloud-init.log:
2017-09-13 18:53:00,118 - __init__.py[DEBUG]: Seeing if we can get any data from <class 'cloudinit.sources.DataSourceCloudStack.DataSourceCloudStack'>
2017-09-13 18:53:00,118 - DataSourceCloudStack.py[DEBUG]: Using /var/lib/dhclient lease directory
2017-09-13 18:53:00,118 - DataSourceCloudStack.py[DEBUG]: No lease file found, using default gateway
Where it then tries to use the default route to download userdata. The problem is that we're not using the Cloudstack VR as a default router, so I expected it to parse /var/lib/dhclient/dhclient--eth0.lease for the "dhcp-server-identifier" line.
Changing it from "dhclient." to "dhclient-" in /usr/lib/python2.7/site-packages/cloudinit/sources/DataSourceCloudStack.py on the running box with an installed RPM did the trick theoretically (after removing the pyc and pyo files, of course).
This *can* be patched around by RedHat/CentOS (and hopefully will), but I figure it might be better to take it straight upstream.
Version-Release number of selected component (if applicable):
CentOS 7.4, cloud-init-0.7.9-9.el7.centos.2.x86_64
This is a replicate of upstream bug /bugs.launchpad .net/cloud- init/+bug/ 1717147
https:/
As requested by customer in support case, I replicate this upstream bug to RHBZ.
Description of problem:
CentOS 7.4 builds on Cloudstack 4.8 don't run cloud-init because the newer version of cloud-init doesn't appear to like the way the dhclient lease file is named.
I've just built a CentOS 7.4 instance in one of my CloudStack 4.8 clusters. Unfortunately, cloud-init fails with the following in snippet in /var/log/ cloud-init. log:
2017-09-13 18:53:00,118 - __init__.py[DEBUG]: Seeing if we can get any data from <class 'cloudinit. sources. DataSourceCloud Stack.DataSourc eCloudStack' > Stack.py[ DEBUG]: Using /var/lib/dhclient lease directory Stack.py[ DEBUG]: No lease file found, using default gateway
2017-09-13 18:53:00,118 - DataSourceCloud
2017-09-13 18:53:00,118 - DataSourceCloud
Where it then tries to use the default route to download userdata. The problem is that we're not using the Cloudstack VR as a default router, so I expected it to parse /var/lib/ dhclient/ dhclient- -eth0.lease for the "dhcp-server- identifier" line.
Theory as to cause: /github. com/cloud- init/cloud- init/commit/ aee0edd93cb4d78 b5e0d1aec71e977 aabf31cdd0# diff-5bc9de2bb7 889d66205845400 c7cf99b) breaks cloud-init beyond the 7.3-distributed cloud-0.7.5 when 7.4 includes 0.7.9-9.
I believe that this change (https:/
Changing it from "dhclient." to "dhclient-" in /usr/lib/ python2. 7/site- packages/ cloudinit/ sources/ DataSourceCloud Stack.py on the running box with an installed RPM did the trick theoretically (after removing the pyc and pyo files, of course).
This *can* be patched around by RedHat/CentOS (and hopefully will), but I figure it might be better to take it straight upstream.
Version-Release number of selected component (if applicable): 0.7.9-9. el7.centos. 2.x86_64
CentOS 7.4, cloud-init-
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: