| 1 |
--- |
| 2 |
fixes: |
| 3 |
- Modifying the extra-specs of an in use Volume Type was something that |
| 4 |
we've unintentionally allowed. The result is unexpected or unknown |
| 5 |
volume behaviors in cases where a type was modified while a volume was |
| 6 |
assigned that type. This has been particularly annoying for folks that |
| 7 |
have assigned the volume-type to a different/new backend device. |
| 8 |
|
| 9 |
In case there are customers using this "bug" we add a config option to |
| 10 |
retain the bad behavior "allow_inuse_volume_type_modification", with a |
| 11 |
default setting of False (Don't allow). Note this config option is being |
| 12 |
introduced as deprecated and will be removed in a future release. It's |
| 13 |
being provided as a bridge to not break upgrades without notice. |