container-sync checks invalid ClientException
Bug #1419901 reported by
Takashi Kajinami
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Critical
|
Eran Rom |
Bug Description
Container-sync checks ClientException when it sends put or delete requests to another swift cluster.
This checking worked well when we used python-swiftclient in container-sync.
However it doesn't work any more today because now container-sync uses internal_client instead of python-swiftclient.
# Unfortunately I cannot find any ClientException in swift.common.
CVE References
Changed in swift: | |
assignee: | nobody → Eran Rom (eranr) |
status: | New → Confirmed |
Changed in swift: | |
status: | Confirmed → In Progress |
Changed in swift: | |
importance: | Undecided → Critical |
To post a comment you must log in.
Confirmed.
In fact I think that that this bug is high importance to anyone trying to deploy Swift with container sync in production, as this can lead to:
1. infinite attempts to delete or put objects in case they were already deleted in the remote side
2. infinite attempts to put objects if the remote side returned 409 rather than 201
and in general not to advance sync_point2
Would appreciate setting the importance accordingly.
Patch is on the way