[openstack-dev] [neutron] duplicate dhcp port when deleting original dhcp port and restart dhcp-agent

Liping Mao -X (limao - YI JIN XIN XI FU WU(SU ZHOU)YOU XIAN GONG SI at Cisco) limao at cisco.com
Thu Jul 10 04:11:26 UTC 2014


This seems a known Issues, and already have some discuss here:
https://bugs.launchpad.net/neutron/+bug/1267310


Regards,
Liping Mao

From: Yangxurong [mailto:yangxurong at huawei.com]
Sent: 2014年7月10日 11:04
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [neutron] duplicate dhcp port when deleting original dhcp port and restart dhcp-agent

Hi, folks,

my testing case is as follows:
1.delete dhcp port
2.restart dhcp-agent

then, there will be double dhcp port.
I’m not sure whether dhcp port should be vied for user and can be deleted, IMO, dhcp port is inner port and thus is not supposed to view for user. Now, if we delete the dhcp port, we will create double dhcp port.
    def enable(self):
        """Enables DHCP for this network by spawning a local process."""
        interface_name = self.device_manager.setup(self.network,
                                                   reuse_existing=True)       ----------->create the first dhcp port
        if self.active:
            self.restart()                                                     ----------->create duplicate dhcp port
        elif self._enable_dhcp():
            self.interface_name = interface_name
            self.spawn_process()
so, alternative solutions:

1.       Dhcp port should not be viewed for user, so , user can’t delete it

2.       Deleting dhcp port and restart the dhcp-agent, we should get network before creating dhcp port rather than passthrough.

Regards,
XuRong Yang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140710/4d23d105/attachment.html>


More information about the OpenStack-dev mailing list