The net, router, and subnet created in the Manila tempest test process are not cleared
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Committed
|
Medium
|
Unassigned |
Bug Description
The code version:Newton
Manila related configuration in tempest.conf.
multitenancy_
create_
default_
image_with_
image_password = manila
capability_
capability_
When the Manila tempest test creates the share, the net,subnet and router will be created.
But when the tempest test was completed, the created net, subnet, and router were not cleaned up.
For example, Executing tempest test:
manila_
the tempest-
When the test execution ends, net, subnet, and router still exist in the environment
This bug has impact on users running local tests as it basically "fills up" their environment with unused network components and can cause issues re-running the tests.
It seems that there is cleanup built into BaseSharesTest's provide_ share_network (lines 417-419) but yet the resources still remain post-test execution.
Attaching examples from:
* Networks
* Subnets
* Routers
* Router ports
* IP address pools
That remain after a few local test runs, using the default Tempest configuration.