tempest

Volume clients fail to initialize if v3 api is disabled

Bug #1714228 reported by Lucian Petrut
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Undecided
Lucian Petrut

Bug Description

In the BaseVolumeTest class, some v3 specific volume clients are accessed even if this API version is not enabled.

This leads to an AttributeError, as shown in the following trace:
http://paste.openstack.org/show/620007/

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

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

Changed in tempest:
assignee: nobody → Lucian Petrut (petrutlucian94)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/499569
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=4f0887c4f2cf484cd77118b86690dd2826ae9961
Submitter: Jenkins
Branch: master

commit 4f0887c4f2cf484cd77118b86690dd2826ae9961
Author: Lucian Petrut <email address hidden>
Date: Thu Aug 31 15:00:24 2017 +0300

    Avoid using v3 volume clients when v3 is disabled

    In the BaseVolumeTest class, some v3 specific volume clients are
    accessed even if this API version is not enabled.

    This change ensures we avoid using them if v3 API is disabled,
    preventing an AttributeError from being raised.

    Change-Id: I0d1f4bfda468d05287dec02137c1842184e66e30
    Closes-Bug: #1714228

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

This issue was fixed in the openstack/tempest 17.1.0 release.

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

Other bug subscribers

Remote bug watches

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