CirrOS cannot get DHCP lease in cloud when CentOS based VM can
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CirrOS |
Incomplete
|
Medium
|
Unassigned |
Bug Description
I am running an all in one Grizzly cloud built with Red Hat Packstack on a single CentOS 6.4 box. The CenTOS box itself is a VMware virtual machine (version 9).
I can successfully deploy VMs using a CEntOS image. The VMs receive their IP address as expected
If I try to deploy a VM using the Cirros image, the VMS do not receive an IP address successfully, the console log shows the following:
Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending select for 10.5.63.4...
Sending select for 10.5.63.4...
Sending select for 10.5.63.4...
No lease, failing
WARN: /etc/rc3.
I have seen a number of people reporting this problem (an IP address is received but then cannot be acknowledge for some reason)
The fact that the pb does not exhibit when booting a CentOS based VM let me thing that this is specific to CirrOS.
Changed in cirros: | |
status: | New → Incomplete |
importance: | Undecided → Medium |
Please configure dnsmasq to log its activity so you can atleast verify what IT thinks about the dhcp traffic.
# openstack-config --set /etc/quantum/ dhcp_agent. ini DEFAULT dnsmasq_config_file /etc/quantum/ dnsmasq. conf
And this goes in the config file: quantum/ dnsmasq. log
log-facility = /data/log/
log-dhcp
You should now be able to see if the instance is offered a IP and what actually happens with the offer.
Tsharking the bridge or namespaced interface could be interesting aswell.