Comment 22 for bug 1652934

Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :

So it seems that setting 'no-kvmapf' on L1 works, tests with that option doesn't fail with any of the symptoms observed earlier in this bug. There are failures anyway, however they doesn't seem related. New failures are reproducable (in two runs it was reproduced) and look like:

-----
    Traceback (most recent call last):
      File "tempest/lib/common/utils/test_utils.py", line 84, in call_and_ignore_notfound_exc
        return func(*args, **kwargs)
      File "tempest/services/object_storage/container_client.py", line 53, in delete_container
        resp, body = self.delete(url)
      File "tempest/lib/common/rest_client.py", line 307, in delete
        return self.request('DELETE', url, extra_headers, headers, body)
      File "tempest/lib/common/rest_client.py", line 664, in request
        self._error_checker(resp, resp_body)
      File "tempest/lib/common/rest_client.py", line 776, in _error_checker
        raise exceptions.Conflict(resp_body, resp=resp)
    tempest.lib.exceptions.Conflict: An object with that identifier already exists
    Details: <html><h1>Conflict</h1><p>There was a conflict when trying to complete your request.</p></html>
-----

More log available [1]

[1] http://paste.openstack.org/show/595048/