Comment 1 for bug 1613316
Revision history for this message
| Stefan Majewsky (stefan-majewsky) wrote Re: container sync produces broken DLOs | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
After further inspection, I now see what is going on. The DLO is copied correctly, but the manifest is not adjusted for the new container name. When the DLO is queried (whether with HEAD or GET), Swift tries to find the segments, but croaks because the container mentioned in the manifest does not exist.
So the actual bug here is that a DLO referring to segments in a non-existing container cannot be interacted with in a meaningful way. (At least HEAD should work IMO.)