This failure occurred on the Dummy driver's driver_handles_share_servers=False gate job in stable/rocky
Change that failed the job: https://review.opendev.org/#/c/688542/1
Logs: https://zuul.opendev.org/t/openstack/build/c34159d5c16d40dca18646ec51a2c944
(Relevant logs are attached with this bug since they will disappear from the log server eventually)
Failure:
{1} manila_tempest_tests.tests.api.admin.test_share_manage_negative.ManageNFSShareNegativeTest.test_manage_share_duplicate [16.104773s] ... FAILED
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/opt/stack/new/manila-tempest-plugin/manila_tempest_tests/tests/api/admin/test_share_manage_negative.py", line 202, in test_manage_share_duplicate
**manage_params
File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 485, in assertRaises
self.assertThat(our_callable, matcher)
File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: <bound method SharesV2Client.manage_share of <manila_tempest_tests.services.share.v2.json.shares_client.SharesV2Client object at 0x7fdf61a52b50>> returned {u'share_type_name': u'tempest-manage-st-name-1002350983', u'links': [{u'href': u'https://192.168.48.33:8786/v2/e4b0ed51fc5a4cfa9f7f1150eeda1d9d/shares/863cd0cf-10ce-4a00-ba1e-04c8f9eb8485', u'rel': u'self'}, {u'href': u'https://192.168.48.33:8786/e4b0ed51fc5a4cfa9f7f1150eeda1d9d/shares/863cd0cf-10ce-4a00-ba1e-04c8f9eb8485', u'rel': u'bookmark'}], u'availability_zone': None, u'share_network_id': None, u'share_server_id': None, u'snapshot_id': None, u'id': u'863cd0cf-10ce-4a00-ba1e-04c8f9eb8485', u'size': None, u'user_id': u'693a334256a245bf92d4e51924c7b989', u'share_type': u'3564fcf9-a40d-4c35-b763-17d81fb866dc', u'project_id': u'e4b0ed51fc5a4cfa9f7f1150eeda1d9d', u'metadata': {}, u'status': u'manage_starting', u'description': None, u'share_group_id': None, u'host': u'ubuntu-xenial-fortnebula-regionone-0012364087@gamma#fake_pool_for_GAMMA', u'revert_to_snapshot_support': False, u'access_rules_status': u'active', u'create_share_from_snapshot_support': False, u'is_public': False, u'task_state': None, u'snapshot_support': True, u'source_share_group_snapshot_member_id': None, u'name': None, u'has_replicas': False, u'replication_type': None, u'created_at': u'2019-10-17T17:52:33.000000', u'share_proto': u'NFS', u'volume_type': u'tempest-manage-st-name-1002350983', u'mount_snapshot_support': False}
The log shows that the manage_share requests are slightly different: 10:/path/ to/fake/ share/share_ d9646569_ 6e03_475c_ b382_76242d73c9 d1_d3b7c0c2_ dac1_4cd6_ 88af_a4e3de8523 d9" 20:/path/ to/fake/ share/share_ d01ca7ad_ 40ac_42e7_ 818b_8758054785 c9_cf0481e7_ 4aa7_4888_ aad0_60eeae208b 56" /github. com/openstack/ manila/ blob/bffeef11b4 aea4a9e718fb781 4336149b1d2abfd /manila/ share/api. py#L618
The first request has the export_path: "export_path": "10.0.0.
The second request has a different export_path: export_path": "10.0.0.
The exception expected by the test should be raised by a conflict found on share creation and validated here: https:/
The issue happens when the export location list has more than one element and its elements are retrieved in a different order.