New Pure Code site is live!
After many months of messing with some very old code, we have launched a revised site for the Pure Code Portal. It is much more minimalistic and cleaner than the old one, and we have plans to add our Code videos and Pure Employee website links in the near future. Have a look and feel free to leave a comment if you would like to see something on the site. https://code.purestorage.com/ Cheers, //Mike35Views2likes1CommentRecently we are getting: "API version does not support
Recently we are getting: "API version does not support setting SafeMode on a protection group." during some of our ansible builds when it is trying to add a volume to a PG that already has safemode enabled. We are on purity 6.7.1 and this has been working for quite a while. This started failing last week I believe and the only software related changes were applying the security_patch_fa_2025_A. Wondering is that messing with the version logic ansible is doing to check if safemode is supported? https://github.com/Pure-Storage-Ansible/FlashArray-Collection/issues/329|https://github.com/Pure-Storage-Ansible/FlashArray-Collection/issues/32988Views0likes1CommentI was referred here by Pure Support regarding an issue
I was referred here by Pure Support regarding an issue with the "volume" function of the Ansible plugin for FlashArray Case Number: CS0053963 Created: Jun 8, 2022 3:04 pm Primary contact: Samuel Lay Description: Here is my playbook: --- - name: Create a Snapshot of Pure volume hosts: all connection: local collections: - purestorage.flasharray gather_facts: no roles: - role: pure_create_clone Here is the role: --- - name: Create Clone of Pure volume purestorage.flasharray.purefa_volume: target: "{{ target }}" name: "{{ volume_name }}" fa_url: "{{ ip }}" api_token: "{{ api_token }}" state: present When I run without size parameter, I get . . . fatal: [syn14p01st001]: FAILED! => {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python3"}, "changed": false, "msg": "Size must be specified to create a new volume"} When I add the size parameter to the role: fatal: [syn14p01st001]: FAILED! => {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python3"}, "changed": false, "msg": "parameters are mutually exclusive: size|target"} Command line: ansible-playbook -l syn14p01st001 -e "target=testvol0" -e "volume_name=clonotesvol00" _pure_create_clone.ym The output from the plugin is mutually exclusive.44Views0likes0CommentsIs there a way to view lower level Fibre Channel diagnostic
Is there a way to view lower level Fibre Channel diagnostic logs from the CLI? We are having an issue with some VMware hosts not getting a response to a PLOGI so they are not able to see any volumes from the Pure array on one of our fabrics. Other storage systems on the same fabric are working fine.38Views0likes0Comments