tearDownClass manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest Failed

Bug #1762900 reported by zhimou.peng
36
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Won't Fix
Low
Unassigned

Bug Description

OS:RHOSP10

Tempest:
[root@osp10unityctl0 log]# rpm -qa|grep tempest
python-sahara-tests-tempest-0.4.1-1.el7ost.noarch
puppet-tempest-9.5.0-3.el7ost.noarch
python-tempest-13.0.0-16.bafe630git.el7ost.noarch
python-tempest-tests-13.0.0-16.bafe630git.el7ost.noarch
openstack-tempest-13.0.0-16.bafe630git.el7ost.noarch

Manila:
[root@osp10unityctl0 log]# rpm -qa|grep manila
openstack-manila-ui-2.5.1-10.el7ost.noarch
openstack-manila-share-3.0.0-11.el7ost.noarch
python-manilaclient-1.11.0-1.el7ost.noarch
python-manila-3.0.0-11.el7ost.noarch
openstack-manila-3.0.0-11.el7ost.noarch
python-manila-tests-3.0.0-11.el7ost.noarch
puppet-manila-9.5.0-3.el7ost.noarch

cases:
[root@osp10unityctl0 test]# cat cases
manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest

[root@osp10unityctl0 test]# tempest run --whitelist-file cases
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-500} \
${PYTHON:-python} -m subunit.run discover -t /usr/lib/python2.7/site-packages/tempest /usr/lib/python2.7/site-packages/tempest/test_discover --list
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-500} \
${PYTHON:-python} -m subunit.run discover -t /usr/lib/python2.7/site-packages/tempest /usr/lib/python2.7/site-packages/tempest/test_discover --load-list /tmp/tmpttL6rp
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_delete_share_network_with_existing_shares [406.621599s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_delete_share_network_with_wrong_type [0.036365s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_delete_share_network_without_id [0.006177s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_get_deleted_share_network [0.230780s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_get_share_network_with_wrong_id [0.035742s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_get_share_network_without_id [0.006946s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_list_share_networks_all_tenants [0.009817s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_list_share_networks_project_id [0.009481s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_list_share_networks_wrong_created_before_value [0.031036s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_list_share_networks_wrong_created_since_value [0.032978s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_update_invalid_keys_sh_server_exists [116.259089s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_update_nonexistant_share_network [0.038059s] ... ok
{0} manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest.test_try_update_share_network_with_empty_id [0.006377s] ... ok
{0} tearDownClass (manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest) [0.000000s] ... FAILED

==============================
Failed 1 tests - output below:
==============================

tearDownClass (manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest)
-----------------------------------------------------------------------------------------------------

Captured traceback:
~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "/usr/lib/python2.7/site-packages/tempest/test.py", line 286, in tearDownClass
        six.reraise(etype, value, trace)
      File "/usr/lib/python2.7/site-packages/tempest/test.py", line 269, in tearDownClass
        teardown()
      File "/usr/lib/python2.7/site-packages/tempest/test.py", line 521, in clear_credentials
        cls._creds_provider.clear_creds()
      File "/usr/lib/python2.7/site-packages/tempest/common/dynamic_creds.py", line 409, in clear_creds
        self._cleanup_default_secgroup(creds.tenant_id)
      File "/usr/lib/python2.7/site-packages/tempest/common/dynamic_creds.py", line 356, in _cleanup_default_secgroup
        nsg_client.delete_security_group(secgroup['id'])
      File "/usr/lib/python2.7/site-packages/tempest/lib/services/network/security_groups_client.py", line 58, in delete_security_group
        return self.delete_resource(uri)
      File "/usr/lib/python2.7/site-packages/tempest/lib/services/network/base.py", line 41, in delete_resource
        resp, body = self.delete(req_uri)
      File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", line 307, in delete
        return self.request('DELETE', url, extra_headers, headers, body)
      File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", line 664, in request
        self._error_checker(resp, resp_body)
      File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", line 776, in _error_checker
        raise exceptions.Conflict(resp_body, resp=resp)
    tempest.lib.exceptions.Conflict: An object with that identifier already exists
    Details: {u'message': u'Security Group 22da942e-90e7-4ad5-aab2-34b269bf2b8a in use.', u'type': u'SecurityGroupInUse', u'detail': u''}

the Security Group 22da942e-90e7-4ad5-aab2-34b269bf2b8a in use.
But I can delete the port which using the Security Group, then delete Security Group.
So my guess is the teardown part is not handle this correctly.

Tags: tempest
Revision history for this message
zhimou.peng (zhimou-peng) wrote :
Sam Wan (sam-wan)
affects: tempest → manila
Changed in manila:
status: New → Triaged
importance: Undecided → High
Tom Barron (tpb)
Changed in manila:
assignee: nobody → Tom Barron (tpb)
Revision history for this message
Goutham Pacha Ravi (gouthamr) wrote :

Hi zhimou.peng (zhimou-peng),

A couple of questions regarding this bug:
1) Have you tried using pre-provisioned credentials, i.e, setting auth.use_dynamic_credentials = False in tempest.conf and using tempest's "accounts.yaml" alternative? [1]
2) Have you tried running these tests on a later version of manila and manila's tempest tests? Your report here is for osp-10, which translates to the Newton release of OpenStack Manila, which is EOL upstream.

[1] https://docs.openstack.org/tempest/latest/configuration.html#pre-provisioned-credentials

Revision history for this message
Goutham Pacha Ravi (gouthamr) wrote :

Okay, this took me a while to reproduce manually with some NetApp gear; I hit the problem you describe with "dynamic credentials"; I recommend configuring tempest with pre-provisioned credentials, and you should not be facing these cleanup issues. Do you have a different workflow for your upstream (Dell EMC Unity) CI?

Tom Barron (tpb)
tags: added: tempest
Revision history for this message
Sam Wan (sam-wan) wrote :

Hi Goutham Pacha Ravi,

Thanks for advice.
We tried 'pre-provisioned credentials’ and it works on RHOSP13. We believe it works on RHOSP10 too but we don't have a RHOPS10 on hand.
Thanks for help.

Revision history for this message
Tom Barron (tpb) wrote :

Setting Status this one to "Won't Fix" since Newton is EOL and the reporter is OK on OSP13 with pre-provisioned credentials.

Changed in manila:
status: Triaged → Won't Fix
Tom Barron (tpb)
Changed in manila:
importance: High → Low
assignee: Tom Barron (tpb) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.