"tacker vnf-delete" not removing dhcp entries from lease file

asked 2017-02-28 23:02:06 -0600

DarkKnight gravatar image

I am creating a VNF that comprises of 5 VDUs. While creation of VNF suceeds, one of the VDUs dont get an IP address. When i digged deeper inside the VM that was not getting an IP, i found that it never received a DHCP offer. Upon further investigating, i found out the problem but dont know how to solve this.

When i issue a tacker vnf-delete <vnf-name>, one of the IP entries in the DHCP lease files is not deleted. As a result when a new instance is assigned the same IP, it gets into a conflict and thus never gets the IP address.

=====

Earlier lease file content: /var/lib/neutron/dhcp/7b8f536f-c364-4f92-8bf0-2db602184fd0/leases
1487848489 fa:16:3e:64:29:d4 192.168.49.19 ta-205f-c11d-4923-be3d-4c5f83303c6b-vdu4-ztbhjidvxgk3 *

After deleting the VNF, contents:  /var/lib/neutron/dhcp/7b8f536f-c364-4f92-8bf0-2db602184fd0/leases
1487848489 fa:16:3e:64:29:d4 192.168.49.19 host-192-168-49-19 *

============

Also interesting to note is that if i manually just create an instance in the openstack and then terminate that, the entries are deleted from the lease file. So, is there an issue with tacker? Also, has anyone encountered a similar issue and how to resolve it?

edit retag flag offensive close merge delete