Comment 4 for bug 1365824

Hi Numan,
 Usually, when people commit to a branch(master/R1.10), they post the
commit or review link for that branch.
Since I saw only the link for master, I opened a new scope for R1.10

I see that Sachin added the commit reference for R1.10

We are fine now..

On 9/17/14, 12:40 AM, "Numan Siddique" <email address hidden> wrote:

>Vedamurthy : This fix is already merged in masterand r1.10.
>I didn't understand why you assigned to r.11.
>In the github i dont see any branch related to r1.11
>Can you please clear my doubt
>
>--
>You received this bug notification because you are a member of Contrail
>Systems engineering, which is subscribed to Juniper Openstack.
>https://bugs.launchpad.net/bugs/1365824
>
>Title:
> IndexAllocator is not deleted when a subnet is deleted
>
>Status in Juniper Openstack distribution:
> New
>Status in OpenContrail:
> Fix Committed
>
>Bug description:
> IndexAllocator is not deleted when a subnet is deleted because of
> which if i delete a subnet and create a new one with same CIDR but
> with different allocation pool, still the old allocation pool is used.
>
> Eg.
> $neutron subnet-create private 10.0.0.0/24 --allocation-pool
>start=10.0.0.2,end=10.0.0.4
> $neutron subnet-delete <SUBNET_ID>
> $neutron subnet-create private 10.0.0.0/24 --allocation-pool
>start=10.0.0.2,end=10.0.0.8
>
> After this, I will not be able to create a port with ip address
> >=10.0.0.5
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/juniperopenstack/+bug/1365824/+subscriptions