Description of problem: I get this test and others failed on multi-nic multi-controller topology with similar context. I checked the logs there are no errors occurred, so I assume this is client version problem such as in the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1290548 setUpClass (tempest.api.volume.test_snapshot_metadata.SnapshotV2MetadataTestJSON) --------------------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "tempest/test.py", line 261, in setUpClass six.reraise(etype, value, trace) File "tempest/test.py", line 254, in setUpClass cls.resource_setup() File "tempest/api/volume/test_snapshot_metadata.py", line 43, in resource_setup cls.snapshot = cls.create_snapshot(volume_id=cls.volume['id']) File "tempest/api/volume/base.py", line 129, in create_snapshot 'available') File "tempest/services/volume/base/base_snapshots_client.py", line 93, in wait_for_snapshot_status old_value = value = self._get_snapshot_status(snapshot_id) File "tempest/services/volume/base/base_snapshots_client.py", line 85, in _get_snapshot_status snapshot_id=snapshot_id) tempest.exceptions.SnapshotBuildErrorException: Snapshot b6c61221-c64a-44a1-b611-2bdacc6a88da failed to build and is in ERROR status Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Evgeny, We can't do much without logs and list of openstack rpms deployed on that environment. A few days we released 7.0.3 which successfully passed all tempest tests in the lab. in your case I don't have any evidence that Tempest actually called Cinder. Please, reopen the case with all relevant information.
*** This bug has been marked as a duplicate of bug 1262064 ***