fixed_ips cannot reliably be released on instance termination
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Chet Burgess | ||
Folsom |
Fix Released
|
High
|
Vish Ishaya |
Bug Description
On rare occasion we have noticed that using nova-network and the VlanManage fixed_ip aren't always marked as free during instance termination until the _disassociate_
The issue occurs as a result of dnsmasq is restarted. On restart the nova-dhcpbridge command is called with the init arguement to populate the dnsmasq lease DB. The lease time, is presently being calculated by taking instances.
If a termination is issued while in this state dnsmasq will receive the release packet and drop it claiming the lease is unknown. As a result nova-dhcpbridge is not called to free the lease in the DB and the IP remains in a partially freed state until the _disassociate_
During normal DHCP operations the fixed_ips.
Changed in nova: | |
assignee: | nobody → Chet Burgess (cfb-n) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → High |
tags: | added: folsom-backport-potential |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/20365
Review: https:/