88d5d18a3d
Hitachi driver with the following patch has lost compatibility of GAD volumes which are created by Hitachi out-of-tree driver until OSP16, because the naming rules of GAD copy group name are different. This patch fixes to have compatibility of GAD volumes by using same naming rule. GAD patch and blueprint: https://review.opendev.org/c/openstack/cinder/+/796170 https://blueprints.launchpad.net/cinder/+spec/hitachi-gad-support Closes-Bug: #2043978 Change-Id: Ie37a0eb8081f5c7a4432d5f390a4d7079ff0e5c9
14 lines
816 B
YAML
14 lines
816 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Hitachi driver `bug #2043978
|
|
<https://bugs.launchpad.net/cinder/+bug/2043978>`_: Since around the Train
|
|
era, Hitachi had an out-of-tree driver that implemented the Global-Active
|
|
Device (GAD) and Remote Replication features. As part of an initiative to
|
|
unify the "Enterprise" and in-tree drivers, change I4543cd036897 in the
|
|
2023.1 (Antelope) release implemented the GAD feature for the in-tree
|
|
driver. Unfortunately, this change used an incompatible string to indicate
|
|
what copy groups were under GAD control, and thus upgrading to the in-tree
|
|
driver breaks GAD for existing volumes. This bug fix makes the copy group
|
|
control identifier consistent so that current users of the out-of-tree
|
|
driver can upgrade to releases that contain the in-tree driver. |