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. ThanksBryan
Hi We are currently using Ansible Modules for Dell EMC PowerMax to verify VMAX configuration changes and other operations.Since the following events occurred, we would like to confirm the operation specifications of the Ansible module. Implementation detailsTwo 10GB volumes and one 20GB volume are created using the following Ansible volume module.→Assumed result: Three new Symdevs will be created, and they will join the StorageGroup specified in the Playbook. Result・A new 10GB Symdev has been created as "00067" and "00068".・A 20GB Symdev has been allocated as "000B3", but an existing Symdev has been allocated.※"000B3" existed on VMAX at 20GB before Ansible was run.it did not belong to any StorageGroup. QuestionAs a behavior of VMAX using Unisphere and SolutionEnabler, when a volume is created, the available young number is automatically selected and a new Symdev is created.In this case where Ansible was executed, only 20GB was not newly created and "000B3" was overwritten.Can you please tell me the working specification of Ansible module? The following is the information about the Ansible module we used. moduleAnsible Modules for Dell EMC PowerMax Version 1.1・dellemc_powermax_volume.pyran in playbook- name: Create volumedellemc_powermax_volume:unispherehost: "{ {unispherehost}}"universion: "{ {universion}}"verifycert: "{ {verifycert}}"user: "{ {user}}"password: "{ {password}}"serial_no: "{ {serial_no}}"vol_name: "{ {vol_name}}"sg_name: "{ {sg_name}}"size: ""cap_unit: "{ {cap_unit}}"state: 'present'
Operating specifications of the Ansible module