The below commit introduced a regression by updating the wrong value to
the attachment field when calling the volume-update swap operation where
the value is now the previous volume ID instead of the current volume
ID. It litterally makes it now imposible to detech the volume from the
instance once it has been swapped (even after the first swap).
Given the original issue can be worked around by detaching and then
attaching the volume before swapping back to the original volume, and
because the original bug only impacts an admin API while here it impacts
a user API, it's preferrable to directly revert the regression and then
work on the next cycle about the root problem rather than leaving the
change and try to fix something which is hard to troubleshoot, also
given the lack of functional tests around the volume operations.
This reverts commit be553fb155.
Change-Id: Ibad1afa5860d611e0e0ea0ba5e7dc98ae8f07190
Closes-Bug: #1625660
ee2c0a00db