[tempest] Tests try to create resources in AZs but fail

Bug #1811739 reported by Goutham Pacha Ravi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Low
Goutham Pacha Ravi

Bug Description

There are many tests that attempt to create shares, replicas and share groups within a specific AZ.

However, the AZ that these tests choose may not support the share type being used.

Test failures from the gate's dummy driver job on https://review.openstack.org/#/c/630039/3 have been added to this bug report.

Sample Failure:

Test link: [1]

manila_tempest_tests.tests.api.test_share_groups.ShareGroupsTest.test_create_sg_and_share_specifying_az_1_sg fails with the following log:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/ddt.py", line 145, in wrapper
    return func(self, *args, **kwargs)
  File "/opt/stack/new/manila-tempest-plugin/manila_tempest_tests/tests/api/test_share_groups.py", line 210, in test_create_sg_and_share_specifying_az
    share_group = self.create_share_group(**sg_kwargs)
  File "/opt/stack/new/manila-tempest-plugin/manila_tempest_tests/tests/api/base.py", line 615, in create_share_group
    client.wait_for_share_group_status(share_group['id'], 'available')
  File "/opt/stack/new/manila-tempest-plugin/manila_tempest_tests/services/share/v2/json/shares_client.py", line 1098, in wait_for_share_group_status
    share_group_id=share_group_id)
manila_tempest_tests.share_exceptions.ShareGroupBuildErrorException: Share group 9653ddbe-443f-47d7-a0ff-00d17879f255 failed to build and is in ERROR status

On inspecting the manila scheduler log, we see that the failure occurred because the capabilities filter failed to find a back end. Before this filter was run, the availability zone filter had isolated just one backend for the resource. The capability filter failure is because the pool supports a different value for "driver_handles_share_servers". The test is merely listing all availability zones and picking the first available one [1]. There is no guarantee that the first availability zone is supported by the share type of the share group.

[1] https://github.com/openstack/manila-tempest-plugin/blob/f6bc6fa/manila_tempest_tests/tests/api/test_share_groups.py#L195

Changed in manila:
importance: Undecided → Low
assignee: nobody → Goutham Pacha Ravi (gouthamr)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila-tempest-plugin (master)

Fix proposed to branch: master
Review: https://review.openstack.org/630886

Changed in manila:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila-tempest-plugin (master)

Reviewed: https://review.openstack.org/630886
Committed: https://git.openstack.org/cgit/openstack/manila-tempest-plugin/commit/?id=839c98b2c1b46c46274e61ead2ef0c55dde35549
Submitter: Zuul
Branch: master

commit 839c98b2c1b46c46274e61ead2ef0c55dde35549
Author: Goutham Pacha Ravi <email address hidden>
Date: Mon Jan 14 23:16:23 2019 -0800

    Fix availability zones tests

    Whenever creating a resource in an availability zone,
    the positive test cases must ensure that the AZ supports
    the characteristics needed by the resource.

    Add a new helper method to filter AZs by share types
    to facilitate such a check.

    Change-Id: Ia721c434ceae5f02fc51bef5ec48b356da0de98d
    Closes-Bug: #1811739

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila-tempest-plugin 0.2.0

This issue was fixed in the openstack/manila-tempest-plugin 0.2.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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