Reviewed: https://review.openstack.org/246795 Committed: https://git.openstack.org/cgit/openstack/vmware-nsx/commit/?id=630b0aebb8021b53d66b37c2971663a1f23ad3b0 Submitter: Jenkins Branch: stable/liberty commit 630b0aebb8021b53d66b37c2971663a1f23ad3b0 Author: Gary Kotton <gkotton at vmware.com> Date: Mon Oct 19 07:36:38 2015 -0700 NSX|V3: create dhcp profile at boot time This profile will be applied to the DHCP ports if the DHCP service is enabled. The change remove the requirement that the admin create this out of band. This is now possible due to the fact that we are using a distributed locking mechanism. Closes-bug: #1507815 Conflicts: vmware_nsx/tests/unit/nsx_v3/test_plugin.py Change-Id: I12538af5849226ae3d8aeaea94bdd80be6ed0605 (cherry picked from commit dd7dd97bed6035f76628394ef60a39471146ae2b) -- You received this bug notification because you are a member of OpenStack Security, which is subscribed to OpenStack. https://bugs.launchpad.net/bugs/1507815 Title: Security group is dropping DHCP packet Status in vmware-nsx: Fix Committed Bug description: The instances launched are not able to get IP addresses because the DHCP packet are dropped by security group. If we open up OS default Block all, instances are able to acquire IP addresses. I saw we only allow DHCP-Client packet in the OS default section. But I believe we should also allow DHCP-Server. To manage notifications about this bug go to: https://bugs.launchpad.net/vmware-nsx/+bug/1507815/+subscriptions