2dc5215321
It is possible for volumes, created from storage pools which have zero-padding disabled, to contain previous data. This change prevents these volumes from being created by default. A user can override this behavior by acknowleding the possibility with a configuration option. This is a squash of the four commits that led to the final state in rocky to not allow the creation of any type of non-zero-padded volumes to be created. This adds a config option that defaults to the safe behavior. It is backporting a new config option, and a change in default behavior, but it should be acceptable in this case so that the security vulnerability can be addressed. Closes-Bug: #1784871 Change-Id: I62f8f48b1624fc9abb7427bd4ca51f7873d35b96 Closes-bug: #1699573 (cherry picked from commit |
||
---|---|---|
.. | ||
scaleio | ||
unity | ||
vnx | ||
__init__.py | ||
test_ps.py | ||
test_vmax.py | ||
test_xtremio.py |