A long time ago the driver was changed to store volume_id
in the nova database and use that. Previously it would use the
volume_name and make a call to get the volume_id.
Both should be supported, but as the code path currently throws
a KeyError it will never reach the backwards compatible code.
This makes sure that the driver works even after an upgrade from Mitaka.
Reviewed: https:/ /review. openstack. org/643092 /git.openstack. org/cgit/ openstack/ os-brick/ commit/ ?id=05b6c9f9fad 15354f598bbd332 a5d56230ece1e0
Committed: https:/
Submitter: Zuul
Branch: master
commit 05b6c9f9fad1535 4f598bbd332a5d5 6230ece1e0
Author: Yury Kulazhenkov <email address hidden>
Date: Wed Mar 13 18:58:50 2019 +0300
Fix ScaleIO KeyError after upgrade
A long time ago the driver was changed to store volume_id
in the nova database and use that. Previously it would use the
volume_name and make a call to get the volume_id.
Both should be supported, but as the code path currently throws
a KeyError it will never reach the backwards compatible code.
This makes sure that the driver works even after an upgrade from Mitaka.
Depends-On: https:/ /review. openstack. org/#/c/ 643130/ 5606c7723dc6c62 bf07fa1d934
Change-Id: Iab6a3ca6bf92dc
Closes-Bug: #1648629