Revert "Set 'serial' to new volume ID in swap volumes"
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 be553fb15591c6fc212ef3a07c1dd1cbc43d6866.
Change-Id: Ibad1afa5860d611e0e0ea0ba5e7dc98ae8f07190
Closes-Bug: #1625660
(cherry picked from commit ee2c0a00db9d6006fb7c3a07ee252d4ca4d73eff)
Reviewed: https:/ /review. openstack. org/374324 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=eae8775f874 bd3ad44febc4a66 984f17540e8b6f
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit eae8775f874bd3a d44febc4a66984f 17540e8b6f
Author: Sylvain Bauza <email address hidden>
Date: Tue Sep 20 16:50:16 2016 +0200
Revert "Set 'serial' to new volume ID in swap volumes"
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 be553fb15591c6f c212ef3a07c1dd1 cbc43d6866.
Change-Id: Ibad1afa5860d61 1e0e0ea0ba5e7dc 98ae8f07190 6fb7c3a07ee252d 4ca4d73eff)
Closes-Bug: #1625660
(cherry picked from commit ee2c0a00db9d600