Bug 1305659
Summary: | ospd-8 poodle 2016-02-04.1 tempest.api.object_storage.test_object_services.ObjectTest.test_update_object_metadata failing | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Steve Linabery <slinaber> |
Component: | openstack-swift | Assignee: | Pete Zaitcev <zaitcev> |
Status: | CLOSED WONTFIX | QA Contact: | nlevinki <nlevinki> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 (Liberty) | CC: | derekh, sgotliv, yeylon, zaitcev |
Target Milestone: | ga | Keywords: | Automation, AutomationBlocker |
Target Release: | 8.0 (Liberty) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-21 09:18:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Steve Linabery
2016-02-08 20:28:18 UTC
The problem appears to be that Tempest isn't getting the new headers back until the copying is complete. For a complicated reason[1], Swift defaults to post-as-copy: every POST request prompts copying of the whole object. Thus, POST operation returns success to the user once the copying is scheduled, but before it completes. In the meanwhile, it's possible to fetch the old data. Tempest does that and fails with a mismatch. It's possible to configure a cluster to run so-called "fast-post" by setting "object_post_as_copy = false" in proxy-server.conf. But I'm sure the cluster is going to fail Tempest elsewhere too, if it's too slow. [1] https://review.openstack.org/135380 |