Manila Tempest Tests - CIFS multi-tenancy tests fail with pre-existing network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Yogesh |
Bug Description
For CIFS - DHSS = True, Manila Tempest Tests need share_network already configured with Security Service before running the tempest tests.
We then specify this share-network in tempest.conf.
However, tempest tests are cleaning up this share network, causing the rest of the tests to fail due to unavailability of CIFS-configured Share Network.
Steps to reproduce -
1. Create a Share Network.
2. Create a Security Service with right configuration of CIFS server.
3. Add Security Service to Share Network that was created in step 1.
4. Add this Share Network Id to tempest.conf under [share] section as a config option - "share_network_id".
5. Also, set "create_
6. Run test_share_
7. At the end of this script, check "manila share-network-
Expected Result - Share Network created earlier should still be available.
Actual Result - The share network is deleted as part of resource clean up.
Now, any tests that require share_network is going to fail.
Workaround -
Comment below 3 lines in base.py -
elif res["type"] is "share_network":
client.
client.
Changed in manila: | |
importance: | Undecided → Medium |
milestone: | none → pike-rc1 |
assignee: | nobody → Yogesh (ykshirsa) |
status: | New → Triaged |
summary: |
- Manila Tempest Tests cleans up share-network causing CIFS multi-tenancy - tests to fail + Manila Tempest Tests - CIFS multi-tenancy tests fail with pre-existing + network |
Fix proposed to branch: master /review. openstack. org/491841
Review: https:/