Purity//FB 4.8.6 FR has released
We are happy to announce the general availability of 4.8.6, the seventh Feature Release in the 4.8/4.9 line, helping customers move from managing storage to managing their data, with governance that enforces itself, a fleet that runs as one, and real-time insight that keeps critical workloads performing, all with less manual effort and less risk. See the release notes for all the details about the features and improvements included in this release.
Flashblade with Splunk OTEL
Hi Team, I have FBS100 in lab environment and Splunk Observability cloud. Done integration on FB end and I got the test results showing as integrated. But somehow the test metrics are not getting populated in Splunk cloud portal. Q1- As per documentation it states adding ingest endpoint of Splunk but only API endpoints works? Does documenation needs an update? Q2 - Is OTEL collector working natively in Purity has been blessed by OTEL vendors like Splunk? Thanks
Flashblade & Ansible collection
Hello community, We are facing some issues with our FlashBlade when provisioning policies with Ansible. We have updated all the components (py-pure-client and the collection), and we are failing on a simple policy deployment. - name: Test purestorage.flashblade.purefb_policy: name: "filesystem_export_policy" enabled: True policy_type: "nfs" at: True client: "mynfsexport.flashblade.local" secure: True security: "sys" permission: "rw" access: "no-squash" fb_url: "{{ fb_host }}" api_token: "{{ fb_api_token }}" The complete stack trace is : The full traceback is: Traceback (most recent call last): File "/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py", line 107, in <module> _ansiballz_main() File "/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py", line 99, in _ansiballz_main invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS) File "/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py", line 47, in invoke_module runpy.run_module(mod_name='ansible_collections.purestorage.flashblade.plugins.modules.purefb_policy', init_globals=dict(_module_fqn='ansible_collections.purestorage.flashblade.plugins.modules.purefb_policy', _modlib_path=modlib_path), File "<frozen runpy>", line 226, in run_module File "<frozen runpy>", line 98, in _run_module_code File "<frozen runpy>", line 88, in _run_code File "/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py", line 4233, in <module> File "/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py", line 4008, in main File "/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py", line 2392, in update_nfs_policy AttributeError: 'ErrorResponse' object has no attribute 'items' fatal: [localhost]: FAILED! => { "changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py\", line 107, in <module>\n _ansiballz_main()\n File \"/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py\", line 99, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py\", line 47, in invoke_module\n runpy.run_module(mod_name='ansible_collections.purestorage.flashblade.plugins.modules.purefb_policy', init_globals=dict(_module_fqn='ansible_collections.purestorage.flashblade.plugins.modules.purefb_policy', _modlib_path=modlib_path),\n File \"<frozen runpy>\", line 226, in run_module\n File \"<frozen runpy>\", line 98, in _run_module_code\n File \"<frozen runpy>\", line 88, in _run_code\n File \"/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py\", line 4233, in <module>\n File \"/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py\", line 4008, in main\n File \"/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py\", line 2392, in update_nfs_policy\nAttributeError: 'ErrorResponse' object has no attribute 'items'\n", "module_stdout": "", "msg": "MODULE FAILURE: No start of json char found\nSee stdout/stderr for the exact error", "rc": 1 } If the policy is already set, the playbook runs perfectly fine. The problem occurs when a new policy is injected. However, we have to install the collection from GitHub. It seems that the artifact built and installed by Ansible Galaxy is not correct. Some commits are not propagated. For example, with the FlashBlade collection 1.24 (installed from Galaxy), we have: >>> from pypureclient.flashblade import ( ... PolicyRuleObjectAccessCondition, ... PolicyRuleObjectAccessPost, ... PolicyRuleObjectAccess, ... NfsExportPolicy, ... NfsExportPolicyRule, ... Policy, ... PolicyPatch, ... PolicyRule, ... SmbSharePolicyRule, ... SmbSharePolicy, ... SmbClientPolicyRule, ... SmbClientPolicy, ... ObjectStoreAccessPolicyPost, ... NetworkAccessPolicy, ... NetworkAccessPolicyRule, ... WormDataPolicy, ... ) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/user/conda/envs/ansible/lib/python3.12/site-packages/pypureclient/flashblade/__init__.py", line 40, in __getattr__ raise ImportError(f'module {__package__} has no attribute {name}') ImportError: module pypureclient.flashblade has no attribute PolicyPatch We have compared the archive from GitHub and there are many differences with the upstream collection code. To help, find my my env package : Package Version ----------------- ----------- annotated-types 0.7.0 ansible-core 2.18.5 bcrypt 5.0.0 certifi 2026.4.22 cffi 2.0.0 cryptography 44.0.0 dnspython 2.8.0 invoke 3.0.3 Jinja2 3.1.4 MarkupSafe 2.1.1 packaging 24.1 paramiko 5.0.0 pip 24.2 py-pure-client 1.88.0 pycparser 2.22 pydantic 2.13.4 pydantic_core 2.46.4 PyJWT 2.12.1 PyNaCl 1.6.2 python-dateutil 2.9.0.post0 PyYAML 6.0.2 resolvelib 1.0.1 setuptools 75.8.2 six 1.17.0 typing_extensions 4.15.0 typing-inspection 0.4.2 urllib3 2.7.0 wheel 0.45.0 And our flashblades are running the Purity//FB 4.6.9. If anyone has a lead to help us get our Ansible back up and running, I thank them in advance. We appreciate your help. MatthAnnouncing the General Availability of Purity//FB 4.7.10 LLR
We are happy to announce the general availability of 4.7.10, the first Long-Life Release (LLR) of the 4.6/4.7 line, providing long-term maintenance of the 4.6 feature set with consistency in capabilities, user experience, and interoperability. For more detailed information about bug fixes and security updates included in each release, see the release notes. Highlights The 4.7 LLR adds many new features and improvements for customers upgrading from the 4.5 LLR: AI and high-performance workload acceleration Major gains for AI, HPC, and other demanding unstructured workloads through higher-performance platform options, increased bandwidth, better read/write concurrency, and S3 over RDMA, provide customers faster time to results, better GPU utilization, and more value from large-scale file and object environments. Lower cost at scale with smarter data placement and efficiency Zero Move Tiering for file and object, larger supported system scale, tenant-level performance controls, and DeepReduce for FlashBlade//E help customers scale capacity more efficiently, improve workload density, and reduce total cost of ownership without adding operational complexity. Stronger security and compliance Important security capabilities including NFS over TLS, mutual TLS, FIDO2 and authentication policy support for SSH, object auditing, and proactive Purity patching, helping customers protect data in flight, strengthen access controls, simplify compliance, and respond faster to risk. Multi-tenancy and service delivery Realms, management access policies, secure multi-tenancy for object, local users and groups, and Fusion workload and preset enhancements give customers stronger isolation, simpler delegated administration, and more consistent service delivery across shared environments and dark sites. Improved observability, resilience, and operations On-box observability, richer protocol and connection statistics, Rapid Replica enhancements, larger-scale file data protection, and hardware-based availability improvements make it easier for customers to troubleshoot faster, protect more data at scale, and run mission-critical environments with greater confidence. This release is supported on the following FlashBlade Platforms: FB//S100, FB//S200 (R1, R2), FB//S500 (R1, R2), FB//ZMT, FB//E, FB//EXA Release recommendations Customers looking for long-term maintenance of the complete 4.6 feature set are encouraged to upgrade to the 4.7 LLR. Customers looking for the latest features as soon as they are available should upgrade to the 4.8 FR. Check out our AI Copilot intelligent assistant for deeper insights into release content and recommendations. EOL schedule The 4.6/4.7 release line is planned to reach End-of-Life (EOL) in April 2029. Links and References Purity//FB 4.7 Release Notes Everpure Product Lifecycle and Support Policies Overview Purity//FB Release and End-of-Life Schedule Purity//FB Release Guidelines FlashBlade Hardware and End-of-Support FlashBlade Capacity and Feature Limits Pure1 Manage AI Copilot
Ask Us Everything about Object Storage
💬 Get ready for our February 2026 edition of Ask Us Everything, this Friday, February 20th at 9 AM Pacific. This month is all about Object Storage. If you have a burning question, feel free to ask it here early and we'll add it to the list to answer tomorrow. Or if we can't get it answered live, our Pure Storage experts can follow up here. Karthik Srinivasan, Flashman & dpoorman are the experts answering your questions during the conversation and here on the community. See you this Friday! (Oh, and if you haven't registered yet, there's still time!) Or, check out this self-serve resource: Object Storage Webinar EDIT: Thanks for joining in! If you have additional burning questions and comments, leave them in the comments below for the team!Announcing the General Availability of Purity//FB 4.6.6
We are happy to announce the general availability of 4.6.6, the seventh release in the 4.6 Feature Release line. See the release notes for all the details about these, and the many other features, bug fixes, and security updates included in the 4.6 release line. UPGRADE RECOMMENDATIONS AND EOL SCHEDULE Customers who are running any previous 4.6 version should upgrade to 4.6.6. Customers who are looking for long-term maintenance of a consistent feature set are recommended to upgrade to the 4.5 LLR. Check out our AI Copilot intelligent assistant for deeper insights into release content and recommendations. Development on the 4.6 release line will continue through February 2026. After this time the full 4.6 feature set will roll into the 4.7 Long Life Release line for long-term maintenance, and the 4.6 line will be declared End-of-Life (EOL). HARDWARE SUPPORT This release is supported on the following FlashBlade Platforms: FB//S100, FB//S200 (R1, R2), FB//S500 (R1, R2), FB//ZMT, FB//E, FB//EXA LINKS AND REFERENCES Purity//FB 4.6 Release Notes Purity//FB Release and End-of-Life Schedule Purity//FB Release Guidelines FlashBlade Hardware and End-of-Support FlashBlade Capacity and Feature Limits Pure1 Manage AI CopilotAnnouncing the General Availability of Purity//FB 4.5.14
We are happy to announce the general availability of 4.5.14, the fifteenth release of the 4.5 Long-Life Release (LLR) line! This LLR line provides long-term maintenance of the complete feature set introduced earlier in the 4.5 release line. For more detailed information about bug fixes and security updates included in each release, see the release notes. UPGRADE RECOMMENDATIONS AND EOL SCHEDULE Customers who are looking for long-term maintenance of the complete 4.5 feature set are encouraged to upgrade to this latest 4.5 LLR. Customers who are looking for continued delivery of all the newest capabilities as soon as they are available should upgrade to the 4.6 Feature Release line. Note, both 3.3 and 4.1 are bridgehead releases, which means any older FlashBlade systems will need to upgrade to 3.3 and then 4.1 before upgrading to 4.5. The 4.5 LLR line will remain active through Q2 2028 before reaching End-of-Life (EOL). HARDWARE SUPPORT This release is supported on the following FlashBladePlatforms: first generation FlashBlade, FB//S100, FB//S200 (R1), FB//S500 (R1), and FB//E. LINKS AND REFERENCES Purity//FB 4.5 Release Notes Purity//FB Release and End-of-Life Schedule Purity//FB Release Guidelines FlashBlade Hardware and End-of-Support FlashBlade Capacity and Feature Limits On Box Diagnostic landing pageAnnouncing the General Availability of Purity//FB 4.6.4
We are happy to announce the general availability of 4.6.4, the fifth release in the 4.6 Feature Release line, continuing to deliver on our Evergreen promise, offering customers new capabilities, improved performance, and increased scale—allowing them to extract even more value from their enterprise data cloud. Some of the Purity features contained in this release include: Readdir contention performance improvement for NFSv4.1 delivers improved directory read performance in EDA, HPC, and AI environments—ensuring reliable, consistent job completion under extreme loads and delivering faster results for critical customer workloads On-box OTEL driven FB File and Object Observability provides deep, actionable insights into fleetwide performance and capacity, with intuitive analytics and historical context—enabling customers to proactively manage growth, optimize availability, and simplify troubleshooting. Rapid Replica: Data eviction and 2K links delivers on-demand policy-driven data retrieval for bandwidth constrained environments, helping slash storage and bandwidth costs while enabling fast, collaborative access to critical data across sites, giving customers agility, automation, and massive scale for efficient, enterprise-wide file sharing. See the release notes for all the details about these, and the many other features, bug fixes, and security updates included in the 4.6 release line. UPGRADE RECOMMENDATIONS AND EOL SCHEDULE Customers who are looking for continued delivery of all the newest capabilities should upgrade to 4.6.4. Customers who are looking for long-term maintenance of a consistent feature set are recommended to upgrade to the 4.5 LLR. Development on the 4.6 release line will continue through February 2026. After this time the full 4.6 feature set will roll into the 4.7 Long Life Release line for long-term maintenance, and the 4.6 line will be declared End-of-Life (EOL) HARDWARE SUPPORT This release is supported on the following FlashBlade Platforms: FB//S100, FB//S200 (R1, R2), FB//S500 (R1, R2), FB//ZMT, FB//E, FB//EXA LINKS AND REFERENCES Purity//FB 4.6 Release Notes Purity//FB Release and End-of-Life Schedule Purity//FB Release Guidelines FlashBlade Hardware and End-of-Support FlashBlade Capacity and Feature Limits On Box Diagnostic landing page
