Previously, when you did not specify parameters when using the role, the role always used the parameters from defaults/main.yml.
Beginning with version 1.3.0, the role interprets unspecified parameters differently depending on the state of pools and volumes that you operate on:
- When creating new pools and volumes, unspecified parameters use the default value from
defaults/main.yml. - When modifying existing pools and volumes, unspecified parameters do not change the settings of the pool or volume. Therefore, to modify an existing pool or volume, you must explicitly specify parameters in the role variables.
Only expect to find LUKS metadata on encrypted volumes.
Fix crash checking for duplicate names when pool has no volumes.
Add empty disk list to pool and volume defaults.
Updated exception message
Confusing error message fix
Non-existent pool removal fix