Closed javierperezatmaerskdotcom closed 1 week ago
@javierperezatmaerskdotcom the documentation bug is fixed in the next release. Can you confirm which Collection version you are currently running?
Sorry if I overshare, just want to make sure you have all reelevate information.
ansible-playbook [core 2.16.8] config file = /etc/ansible/ansible.cfg configured module search path = ['/home/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python3/dist-packages/ansible ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections executable location = /usr/bin/ansible-playbook python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/usr/bin/python3) jinja version = 3.0.3 libyaml = True
Collection Version
amazon.aws 7.6.1
ansible.netcommon 5.3.0
ansible.posix 1.5.4
ansible.utils 2.12.0
ansible.windows 2.4.0
arista.eos 6.2.2
awx.awx 23.9.0
azure.azcollection 1.19.0
check_point.mgmt 5.2.3
chocolatey.chocolatey 1.5.1
cisco.aci 2.9.0
cisco.asa 4.0.3
cisco.dnac 6.16.0
cisco.intersight 2.0.9
cisco.ios 5.3.0
cisco.iosxr 6.1.1
cisco.ise 2.9.2
cisco.meraki 2.18.1
cisco.mso 2.6.0
cisco.nxos 5.3.0
cisco.ucs 1.10.0
cloud.common 2.1.4
cloudscale_ch.cloud 2.3.1
community.aws 7.2.0
community.azure 2.0.0
community.ciscosmb 1.0.9
community.crypto 2.20.0
community.digitalocean 1.26.0
community.dns 2.9.2
community.docker 3.10.4
community.general 8.6.2
community.grafana 1.9.1
community.hashi_vault 6.2.0
community.hrobot 1.9.3
community.library_inventory_filtering_v1 1.0.1
community.libvirt 1.3.0
community.mongodb 1.7.4
community.mysql 3.9.0
community.network 5.0.3
community.okd 2.3.0
community.postgresql 3.4.1
community.proxysql 1.5.1
community.rabbitmq 1.3.0
community.routeros 2.16.0
community.sap 2.0.0
community.sap_libs 1.4.2
community.sops 1.6.7
community.vmware 4.4.0
community.windows 2.2.0
community.zabbix 2.5.1
containers.podman 1.15.2
cyberark.conjur 1.3.0
cyberark.pas 1.0.25
dellemc.enterprise_sonic 2.4.0
dellemc.openmanage 8.7.0
dellemc.powerflex 2.5.0
dellemc.unity 1.7.1
f5networks.f5_modules 1.28.0
fortinet.fortimanager 2.5.0
fortinet.fortios 2.3.6
frr.frr 2.0.2
gluster.gluster 1.0.2
google.cloud 1.3.0
grafana.grafana 2.2.5
hetzner.hcloud 2.5.0
hpe.nimble 1.1.4
ibm.qradar 2.1.0
ibm.spectrum_virtualize 2.0.0
ibm.storage_virtualize 2.3.1
infinidat.infinibox 1.4.5
infoblox.nios_modules 1.6.1
inspur.ispim 2.2.3
inspur.sm 2.3.0
junipernetworks.junos 5.3.1
kaytus.ksmanage 1.2.2
kubernetes.core 2.4.2
lowlydba.sqlserver 2.3.3
microsoft.ad 1.6.0
netapp.aws 21.7.1
netapp.azure 21.10.1
netapp.cloudmanager 21.22.1
netapp.elementsw 21.7.0
netapp.ontap 22.11.0
netapp.storagegrid 21.12.0
netapp.um_info 21.8.1
netapp_eseries.santricity 1.4.0
netbox.netbox 3.19.1
ngine_io.cloudstack 2.3.0
ngine_io.exoscale 1.1.0
openstack.cloud 2.2.0
openvswitch.openvswitch 2.1.1
ovirt.ovirt 3.2.0
purestorage.flasharray 1.28.1
purestorage.flashblade 1.17.0
purestorage.fusion 1.6.1
sensu.sensu_go 1.14.0
splunk.es 2.1.2
t_systems_mms.icinga_director 2.0.1
telekom_mms.icinga_director 1.35.0
theforeman.foreman 3.15.0
vmware.vmware_rest 2.3.1
vultr.cloud 1.13.0
vyos.vyos 4.1.0
wti.remote 1.0.5
I realize what the issue was. I was using "pgroup" instead of "add_to_pgs". Looks like pgroup is supposed to be deprecated??? still not sure on that. Instead of reading the options I went straight to the examples, and that's where I think I went wrong. It was easy enough to figure out.
In the below part of the examples, the protection group variable should be pgroup, but it is prgoup. Also not sure if it really works. I have tried it, but manually have to add the volume to the protection group after it creates the volume.
The below is the part I ran and it creates the volume, but it doesn't add it to the protection group. I have the var listed like this in the file pure_protection_group: protectiongroupname .
name: Create and connect Volume hosts: localhost gather_facts: false vars_files:
tasks: