If cleanup fails on a group delete, the next new group created is unusable

Bug #1508726 reported by Magesh GV
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy
New
Medium
Robert Kukura

Bug Description

Due to some issue, most likely VMs/Router ports present on a group, the group delete failed to clean up the subnet and the network.

The next group create went ahead and reused the old subnet CIDR which is still present on Neutron. The RMD does not consider these stale subnets left behind.
https://github.com/openstack/group-based-policy/blob/stable/juno/gbpservice/neutron/services/grouppolicy/drivers/resource_mapping.py#L1446

As a result, configuring the new subnet failed on Apic because of a overlapping CIDR and resolving arp for this subnet's router IP fails in the leaf.

Either the group delete has to make sure all the resources are cleaned up, or the subnet allocation should take this subnet leakage into consideration.

summary: - [apic mapping] If cleanup fails on a group delete, the next new group
- created is unusable
+ If cleanup fails on a group delete, the next new group created is
+ unusable
Changed in group-based-policy:
importance: Undecided → Medium
milestone: none → liberty-1
assignee: nobody → Robert Kukura (rkukura)
Changed in group-based-policy:
milestone: liberty-1 → next
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.