mid-upgrade clusters can cause versioned write errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Medium
|
Tim Burke |
Bug Description
If a cluster has pre-2.6.0 container servers and post-2.6.0 proxy servers, then DELETE'ing from a versioned writes container will cause the oldest version to replace the current object instead of the newest version.
The reason is because the upgraded proxy server makes a reverse=True request to the container server and assumes the results it gets back are actually reversed. But the older container server ignores the reverse query parameter and return the results in normal order.
This can be mitigated by ensuring that container servers are upgraded before proxy servers.
A more permanent fix would be for the proxy to attempt determination of the order of the response from the container server and do the right thing.
Changed in swift: | |
assignee: | nobody → Tim Burke (1-tim-z) |
Fix proposed to branch: master /review. openstack. org/299686
Review: https:/