RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1274308 - Consistently occurring swift related failures in RDO with a HA deployment
Summary: Consistently occurring swift related failures in RDO with a HA deployment
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-swift
Version: Liberty
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: Pete Zaitcev
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-22 13:13 UTC by Attila Darazs
Modified: 2021-09-29 15:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:39:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Attila Darazs 2015-10-22 13:13:16 UTC
Description of problem:
We're running Tempest smoke test on the latest RDO liberty (deployed with rdo-manager on a virthost) and the test in summary fails consistently in a HA deployment, while passing in a non-HA setup.

I opened the bug against swift, because I don't know which HA component can be the reason for the failures, but the problem might not be swift itself.

Failing tests:

tempest.api.object_storage.test_container_services.ContainerTest.test_create_container, error message:

tempest_lib.exceptions.Conflict: An object with that identifier already exists

tempest.api.object_storage.test_object_services.ObjectTest.test_update_object_metadata, error message:

testtools.matchers._impl.MismatchError: 'x-object-meta-test-meta' not in {'status': '200', 'content-length': '4', 'content-location': 'http://192.0.2.6:8080/v1/AUTH_9c2120b4f2d24cab817345598fb9e0dd/tempest-TestContainer-1119601688/tempest-TestObject-1732508500', 'accept-ranges': 'bytes', 'last-modified': 'Thu, 22 Oct 2015 04:46:48 GMT', 'connection': 'close', 'etag': '098f6bcd4621d373cade4e832627b4f6', 'x-timestamp': '1445489207.27781', 'x-trans-id': 'tx20b3d9fdcd284ada86d4e-0056286a37', 'date': 'Thu, 22 Oct 2015 04:46:47 GMT', 'content-type': 'application/json'}

Version-Release number of selected component (if applicable):
openstack-swift-object-2.4.1-dev70.el7.centos.noarch

How reproducible:
3 of out of the last 3 tests failed with these errors.

Steps to Reproduce:
1. HA deployment with rdo-manager
2. Run Tempest smoke tests

Additional info:
Please find all the detailed logs attached to this job run:

https://ci.centos.org/view/rdo/job/rdo_manager-periodic-7-rdo-liberty-delorean_mgt-centos-7.0-templates-virthost-minimal_ha-neutron-ml2-vxlan-smoke/59/#showFailuresLink

You can find all the service logs, package versions in /var/log/rpm.list, etc. for all nodes.

Please let me know if you need more information.

Comment 1 Alan Pevec 2015-12-05 00:38:12 UTC
Hi Pete, can you have a look if this belongs to Swift or component should be moved to somewhere else?

Comment 2 Evgeny 2015-12-22 18:30:21 UTC
Just want to add other tests failing with the same signature
 tempest.api.identity.admin.v2.test_roles_negative
tempest.api.identity.admin.v2.test_users_negative

raceback (most recent call last):
  File "tempest/api/identity/admin/v2/test_users_negative.py", line 90, in test_create_user_request_without_a_token
    self.data.tenant['id'], self.alt_email)
  File "/opt/ws/tempest/.tox/full/lib/python2.7/site-packages/testtools/testcase.py", line 422, in assertRaises
    self.assertThat(our_callable, matcher)
  File "/opt/ws/tempest/.tox/full/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: <bound method IdentityClientJSON.create_user of <tempest.services.identity.v2.json.identity_client.IdentityClientJSON object at 0x80a8d10>> returned {u'username': u'test_user-83622701', u'email': u'test_user-83622701', u'name': u'test_user-83622701', u'enabled': True, u'id': u'18ebc77a4bb64da1942d215feebe91af', u'tenantId': u'de859fafb4ea498c99569dc315e75261'}


Appears to me an API issue. I have similar deployment parameters

Comment 3 Chandan Kumar 2016-05-19 15:39:38 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


Note You need to log in before you can comment on or make changes to this bug.