when neutron-dhcp-agent dies / moves dnsmasq is left running
Bug #1285929 reported by
Andrew Woodward
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Sergey Vasilenko | ||
4.1.x |
Fix Released
|
High
|
Sergey Vasilenko | ||
5.0.x |
Fix Released
|
High
|
Sergey Vasilenko |
Bug Description
When neutron-dhcp-agent is killed by SIGTERM or SIGKILL all of the dnsmqsq processes are left running. When neutron-dhcp-agent restarts it will remove dnsmasq instances if it starts on the same node, however when neutron-dhcp-agent is moved to another controller then dnsmqsq us permanently orphaned. According to report in IRC this caused failures to receive DHCP addresses untill crm was ordered to restart neutron-dhcp-agent again.
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Sergey Vasilenko (xenolog) |
tags: | added: backports-4.1.1 |
tags: | added: ha |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
You should not perform such actions as killing of agent processes except you do all the additional cleanup steps (rescheduling of messages, port cleanup, killing dnsmasq instances and so on) by yourself. We can provide more reliable OCF resource agent for neutron services, though, but this can be left for the next release.