Description of problem: If you stop the neutron-dhcp-agent, start a new VM, then start neutron-dhcp-agent, the new config file isn't set with new lease, so, the new VM won't find DHCP unless a new VM is started afterwards. This regression is introduced by the process monitor patch I backported. Version-Release number of selected component (if applicable): openstack-neutron-2014.1.3-9.el6ost openstack-neutron-2014.1.3-8.el7ost starting at openstack-neutron-2014.1.3-4.el7ost How reproducible: 100% Steps to Reproduce: 1. stop neutron-dhcp-agent 2. start a new VM, and wait 10-20 seconds 3. start neutron-dhcp-agent 4. try to reboot, start/stop the VM, no success with DHCP 5. Add a new VM to same network, this one will get DHCP 6. Restart the first VM, it will get DHCP now Actual results: VM doesn't get dhcp if it was started on the middle of a restart. because leases aren't updated. dhcp_agent.log will have something like: 2014-11-12 13:16:54.422 23588 DEBUG neutron.agent.linux.utils [req-b123e47f-d42e-4cce-a989-7845168a7acb None] Unable to access /var/lib/neutron/external/pids/74124f90-5fbf-48f2-b2c9-36dbd109ad7d.pid.dnsmasq get_value_from_file /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:162 Expected results: VM get's dhcp as the dhcp-agent restart may update the leases. Additional info:
Tested in Rhel7 AIO + Compute node OpenStack/5.0-RHEL-7/2014-11-14.1 openstack-neutron-2014.1.3-10.el7ost.noarch openstack-neutron-ml2-2014.1.3-10.el7ost.noarch openstack-neutron-metering-agent-2014.1.3-10.el7ost.noarch openstack-neutron-openvswitch-2014.1.3-10.el7ost.noarch Steps to Reproduce: 1. stop neutron-dhcp-agent 2. start a new 4 VMs, and wait 20-30 seconds 3. start neutron-dhcp-agent 4. reboot the VMs 5. All VMs are assigned IP successfully
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2014-1942.html