multiple epg using same L2P fails to allocate unique subnet

Bug #1570121 reported by puppet-py
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy
New
High
Unassigned

Bug Description

Create an L3P is created with subnet-prefix-length 30
Create an L2P associating to the above L3P
Now create an EPG and associate to above L2P. Exhaust the available IPs by allocating a VM on this EPG
Create the 2nd EPG associating to the above L2P

Observation: Both EPGs point to the same neutron subnet and thereby no new end-points can be brought up on the 2nd EPG

Version: Kilo, Liberty

Tags: gbp
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.