Before this update, when retyping `in-use` Red Hat Ceph Storage (RHCS) volumes to store the volume in a different pool than its current location, data could be corrupted or lost. With this update, the Block Storage RHCS back end resolves this issue.
Created attachment 1979481[details]
reproduction notes
Description of problem:
Volume retype of an in-use RBD volume moves the RBD image but does not update location in the instance using the volume.
Steps to Reproduce:
1. Have an RBD volume attached to an instance
2. Retype w/ migrate the volume to a type that moves it to a different RBD pool (different c-vol backend)
3. Observe the RBD volumes' location (rbd ls volumes) vs. the location in the instance VM (virsh dumpxml).
4. Reboot the instance w/ openstack server reboot
Actual results:
Instance cannot boot.
Additional info:
The upstream bug contains more detailed notes on reproduction:
https://bugs.launchpad.net/cinder/+bug/2019190https://paste.openstack.org/raw/bNpzkjbeXrmTCwNHfDGs/
After some manual application of the manual steps which confirmed the verification, the scenario was verified the additional confirmation of running the tests from the WIP tempest and cinder-tempest-plugin patches which can reproduce the problem, namely:
- https://review.opendev.org/c/openstack/tempest/+/890360
- https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/894189
All those tests pass now (failing before). Kudos to Yosi for most of the verification.
openstack-cinder-18.2.2-1.20230518161045.el9ost.noarch
python3-cinder-18.2.2-1.20230518161045.el9ost.noarch
python3-cinder-common-18.2.2-1.20230518161045.el9ost.noarch
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1.1 (Wallaby)), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:5138