| 1 |
--- |
| 2 |
upgrade: |
| 3 |
- | |
| 4 |
This release introduces a new configuration option, |
| 5 |
``vmdk_allowed_types``, that specifies the list of VMDK image |
| 6 |
subformats that Cinder will allow. The default setting allows |
| 7 |
only the 'streamOptimized' and 'monolithicSparse' subformats, |
| 8 |
which do not use named extents. |
| 9 |
security: |
| 10 |
- | |
| 11 |
This release introduces a new configuration option, |
| 12 |
``vmdk_allowed_types``, that specifies the list of VMDK image |
| 13 |
subformats that Cinder will allow in order to prevent exposure |
| 14 |
of host information by modifying the named extents in a VMDK |
| 15 |
image. The default setting allows only the 'streamOptimized' |
| 16 |
and 'monolithicSparse' subformats, which do not use named extents. |
| 17 |
- | |
| 18 |
As part of the fix for `Bug #1996188 |
| 19 |
<https://bugs.launchpad.net/cinder/+bug/1996188>`_, cinder is now more |
| 20 |
strict in checking that the ``disk_format`` recorded for an image (as |
| 21 |
revealed by the Image Service API image-show response) matches what |
| 22 |
cinder detects when it downloads the image. Thus, some requests to |
| 23 |
create a volume from a source image that had previously succeeded may |
| 24 |
fail with an ``ImageUnacceptable`` error. |
| 25 |
fixes: |
| 26 |
- | |
| 27 |
`Bug #1996188 <https://bugs.launchpad.net/cinder/+bug/1996188>`_: |
| 28 |
Fixed issue where a VMDK image file whose createType allowed named |
| 29 |
extents could expose host information. This change introduces a new |
| 30 |
configuration option, ``vmdk_allowed_types``, that specifies the list |
| 31 |
of VMDK image subformats that Cinder will allow. The default |
| 32 |
setting allows only the 'streamOptimized' and 'monolithicSparse' |
| 33 |
subformats. |