It is possible that the volume size in integration test is fetched before volume finishes to extend

[Timur Sufiev]

As a result, if volume takes a bit longer to extend and Selenium is fast enough, Selenium fetches old volume size while the volume is extending. This results in a test failure.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/324370
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=873a761511f84b71d5496b1182f10f1a249fe8f8
Submitter: Jenkins
Branch: master

commit 873a761511f84b71d5496b1182f10f1a249fe8f8
Author: Timur Sufiev <email address hidden>
Date: Thu Jun 2 14:10:52 2016 +0300

    In integration tests prevent getting volume size too early

    In the test_volume_extend it was possible for a new volume size to be
    fetched while the volume itself was still being extended, giving an
    old size and failing a test as a result. Fix this intermittent failure
    by waiting till the volume becomes 'Available' (and no longer
    'Extending') before fetching its new size.

    Closes-Bug: #1588307
    Change-Id: I7197904dccd842eb4ef8931208b50ba2144c1a8c

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/horizon 10.0.0.0b2 development milestone.