This causes resource leakage in Tempest. HA networks aren't cleaned, and, when using limited VNI range, or VLAN range, Tests will start failing once limit is reached. Suggestion: Introduce a cleaner to the tenant (not router!) cleanup code:
1. search for the HA network of this tenant (neutron net-list --tenant-id " ") **note that the network has empty tenant-id but the tenant it belongs to is part of the network name. 2. if exist, log a warning. 3. if CONF.network.cleanup_l3_ha: delete the network This has to be logged and has to be turned off by default. ** Also affects: tempest Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1367157 Title: HA network remains even if there is no more HA router Status in neutron: Confirmed Status in tempest: New Bug description: Currently when the last HA router of a tenant is deleted the HA network belonging to this tenant is not removed. This is the case in the rollback of a router creation and in the delete_router itself. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1367157/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp