scenario004 failing: 'Manager' object has no attribute 'volumes_v2_client'

Bug #1714577 reported by Emilien Macchi on 2017-09-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Critical
Emilien Macchi

Bug Description

Running Tempest on scenario004:

ft1.1: setUpClass (tempest.scenario.test_network_basic_ops.TestNetworkBasicOps)_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/tempest/test.py", line 251, in setUpClass
    six.reraise(etype, value, trace)
  File "/usr/lib/python2.7/site-packages/tempest/test.py", line 241, in setUpClass
    cls.setup_clients()
  File "/usr/lib/python2.7/site-packages/tempest/scenario/manager.py", line 82, in setup_clients
    cls.volumes_client = cls.os_primary.volumes_v2_client
AttributeError: 'Manager' object has no attribute 'volumes_v2_client'

http://logs.openstack.org/26/499626/1/check/gate-tripleo-ci-centos-7-scenario004-multinode-oooq/44bf3e9/logs/tempest.html.gz

Changed in tripleo:
importance: Undecided → Critical
Emilien Macchi (emilienm) wrote :

Here's what we did so far: merge https://review.rdoproject.org/r/#/c/9176/ so we pin Tempest to 17.0.0 and see how it works.

If it doesn't work, we should revert https://review.openstack.org/#/c/491113/

Changed in tripleo:
assignee: nobody → Emilien Macchi (emilienm)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers