It appears that the 1.0 version of the modules exhibit this behavior as I was able recreate the problem with the volumes module from that release. After upgrading to the latest version 1.3 the problem went away and a new volume was created every time as appropriate.
I have made engineering aware of this issue, and have asked that they look into it deeper. When there is more info from them, you should see another reply.
To add further info to the device selection process in the newer release configuration, the following was an explanation given to engineering:
*****
To fully explain the device selection on the API if a new device is not being created the API will seek to reuse existing devices. This is advantageous in that we don’t create any new device and consume more meta data un-necessarily. If a matching device that is not in use can not be found the API will create a new device.
The criteria for automatic device selection is as follows:
Devices are considered to be not in use
Not in a storage group
Not linked to a SnapVX snapshot
Not in an active replication session
Does not have a label
Not mapped to any front end ports
With the criteria above you can safely assume that the ansible modules, even if they do select an existing device will not have an impact on any customer data. Re-Use of devices does not wipe any existing data, if a customer wishes to do this then as part of their reclaim operations they should do a free on the devices or simply delete when they are being decommissioned.
bmcfeeters
1 Rookie
•
72 Posts
0
January 5th, 2021 08:00
Hello,
It appears that the 1.0 version of the modules exhibit this behavior as I was able recreate the problem with the volumes module from that release. After upgrading to the latest version 1.3 the problem went away and a new volume was created every time as appropriate.
Thanks
Bryan
FoolInTheRain
123 Posts
0
January 4th, 2021 08:00
I have made engineering aware of this issue, and have asked that they look into it deeper. When there is more info from them, you should see another reply.
v_koji.i_s
13 Posts
0
January 8th, 2021 03:00
Thank you for your reply.
The same content is reproduced,
It turns out that this content has been improved in version1.3.
FoolInTheRain
123 Posts
0
January 13th, 2021 09:00
To add further info to the device selection process in the newer release configuration, the following was an explanation given to engineering:
*****
To fully explain the device selection on the API if a new device is not being created the API will seek to reuse existing devices. This is advantageous in that we don’t create any new device and consume more meta data un-necessarily. If a matching device that is not in use can not be found the API will create a new device.
The criteria for automatic device selection is as follows:
With the criteria above you can safely assume that the ansible modules, even if they do select an existing device will not have an impact on any customer data. Re-Use of devices does not wipe any existing data, if a customer wishes to do this then as part of their reclaim operations they should do a free on the devices or simply delete when they are being decommissioned.
****