Tempest tests for consistency groups are slow

Bug #1493406 reported by Valeriy Ponomaryov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Medium
Valeriy Ponomaryov

Bug Description

Recently merged feature for consistency groups was covered with Tempest API tests, see [1]. And resources there are created one by one that is very slow. This can be fixed by using already existing base methods.

[1] https://review.openstack.org/#/c/215346/

Tags: tempest
tags: added: tempest
Changed in manila:
importance: Undecided → Medium
Changed in manila:
assignee: nobody → Valeriy Ponomaryov (vponomaryov)
milestone: none → mitaka-1
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.openstack.org/247052
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=429bd1fec6eeb2bbeed24fef6574aec5ee1b21ae
Submitter: Jenkins
Branch: master

commit 429bd1fec6eeb2bbeed24fef6574aec5ee1b21ae
Author: Valeriy Ponomaryov <email address hidden>
Date: Wed Nov 18 19:17:46 2015 +0200

    Improve Tempest tests for consistency groups

    Resource setup for 'ConsistencyGroupActionsTest' test class is
    inefficient. It creates three separate shares waiting for 'available'
    status going one by one. It can be improved by creating three shares
    at once and then waiting for their status. So, update resource setup
    for mentioned class and do related minor updates for tests of that
    class.

    Change-Id: Ibd82796866851cba22b417fad34f41dc2aa756e8
    Closes-Bug: #1493406

Changed in manila:
status: In Progress → Fix Committed
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/manila 2.0.0.0b1

This issue was fixed in the openstack/manila 2.0.0.0b1 development milestone.

Changed in manila:
status: Fix Committed → Fix Released
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.