Skip to main content
Pure Technical Services

vROps 3.x Management Pack Release Notes

Currently viewing public documentation. Please login to access the full scope of documentation.

Release Timeline

The following table outlines the release status and release date for the most recent release. 

Management Pack Version Release Status Release Date Supported Purity Versions Supported vROps Versions
3.1.1 General Availability March 19, 2021 5.1+ 8.0, 8.1, 8.2, 8.3
3.0.2 General Availability September 8, 2020 5.1+ 8.0, 8.1, 8.2, 8.3
3.0.1 Available Upon Request July 6, 2020 5.1+ 8.0, 8.1
3.0.0 Available Upon Request April 15, 2020 5.1+ 8.0, 8.1

Unless explicitly noted, all minor revision updates of vROps are supported if the major version is listed.

3.1.1 Release Notes

Release: March 19, 2021

Fixes

Bandwidth Write Workload % and Bandwidth Read Workload % corrected (CSG-1230)

These workload metrics were previously flipped and resulted in inaccuracies in the displaying of this data.

Auto Discovery re-enables previously disabled inventory items

After disabling an inventory item from collecting, if the array object had Auto Discovery set to True, the previously disabled inventory item would start collecting again.

Enhancements

  • vVol container objects now displayed and have relationships in the vROps management pack (CSG-888, CSG-1213) 

  • Enable/disable collection on FlashArray objects (CSG-579)

Known Limitations / Issues

-There are no known limitations or issues in this version of vROps Management Pack.

3.0.2 Release Notes

Release: September 8, 2020

Fixes

Addresses an issue where collection times run longer than expected which may result in specific API calls timing out to vCenter / vROps (CSG-635 / CSG-695).

The inconsistency in job run times is a result of out-dated / deprecated APIs used from the Pure Storage Management Pack (MP) to the vROps server. This issue has been resolved by removing all of the deprecated APIs and replaced with up-to-date and more efficient API queries.

Enhancements

- No new enhancements reported in this version of vROps Management Pack.

Known Limitations / Issues

  • NVMe-oF backed datastores appear in vROps but not in all Pure Storage Management Pack dashboards (CSG-607)

With the release of vSphere 7 VMware introduced the ability to connect to ESXi host via NVMe-RoCE and NVMe-FC. The Pure Storage Management Pack dashboards do not populate the NVMe-oF backed datastores. 

Workaround: None

  • vVol datastores / Protocol Endpoints (PEs) do not show up in the Pure Storage dashboards or statistics (CSG-608)

The Pure Storage Management Pack does not show vVol datastores in the dashboards or report any statistics. 

Workaround: None

3.0.1 Release Notes

Release: July 6, 2020

Fixes

Addresses an issue where installing the Pure Storage Management Pack on vROps 8.1 resulted in an unexpected Python error (CSG-551).

Installation on vROps 8.1 is now successful with no errors and all logging from the Pure Storage Management Pack is available.

Addresses an issue where error "Adapter instance object has error status" is reported in vROps when using virtual volumes (vVols) (CSG-623)

Virtual Volumes (vVols) are now able to be successfully destroyed on the FlashArray while a vROps discovery job is running without crashing the Pure Storage Management Pack. This issue was typically reported during backup jobs involving vVols. 

Addresses an issue where vROps erroneously reports alert "Objects are not receiving data from adapter instance" (CSG-622)

Due to a change in vROps 8.x some objects associated with the Pure Storage FlashArray were erroneously reporting that they had become stale and were no longer receiving updates from the Pure Storage Management Pack. This issue is further described here. This issue has been resolved.

Addresses an issue where all URLs associated with alerts were directed to an invalid webpage (CSG-205)

All links have been updated to point to the most recent Pure Storage Knowledge Base articles for all FlashArray alerts.

Enhancements

  • Fibre Channel (FC) alerts triggered on the Pure Storage FlashArray are now reported in vROps. Previously these alerts were not reported if it was opened and closed between the 5 minute discovery intervals within the Management Pack. (CSG-166)
  • New alert definitions added along with outdated alerts removed.
  • All latency metrics are reported in milliseconds (ms) by default rather than microseconds (µs) resulting in consistent reporting between vROps and the FlashArray.

Known Limitations / Issues

  • NVMe-oF backed datastores appear in vROps but not in all Pure Storage Management Pack dashboards (CSG-607)

With the release of vSphere 7 VMware introduced the ability to connect to ESXi host via NVMe-RoCE and NVMe-FC. The Pure Storage Management Pack dashboards do not populate the NVMe-oF backed datastores. 

Workaround: None

  • vVol datastores / Protocol Endpoints (PEs) do not show up in the Pure Storage dashboards or statistics (CSG-608)

The Pure Storage Management Pack does not show vVol datastores in the dashboards or report any statistics. 

Workaround: None

  • FlashArray adapter logs report "Could not send 'Get Relationships' task to Controller" resulting in failed collection cycles (CSG-695)

After configuring a FlashArray adapter for metrics collection the adapter fails and reports "Could not send 'Get Relationships' task to Controller". This issue is actively being investigated with no underlying cause determined.

Workaround: In some instances removing the impacted FlashArray adapter and re-adding it resolves the issue.

3.0.0 Release Notes

Release: April 15, 2020

Fixes

Addresses an issue where average bandwidth for read and write operations on Pure Storage objects are incorrect (CSG-203)

While reviewing performance metrics for Pure Storage FlashArrays and volumes, the read and write bandwidth is reporting the values in TB/s rather than MB/s. A change to the underlying formula has corrected this issue.

Enhancements 

  • Support for vROps 8.0 and 8.1

Known Limitations / Issues

  • Alert definitions resolve to invalid URLs (CSG-205)

vROps has outdated URLs that no longer point to the correct support links. When the links are clicked from vROps an invalid page will be populated.

Workaround:  Locate the Alert number reported in vROps and then go to the Purity//FA Alerts KB to determine which actions should be taken.

  • NVMe-oF backed datastores appear in vROps but not in all Pure Storage Management Pack dashboards (CSG-607)

With the release of vSphere 7 VMware introduced the ability to connect to ESXi host via NVMe-RoCE and NVMe-FC. The Pure Storage Management Pack dashboards do not populate the NVMe-oF backed datastores. 

Workaround: None

  • vVol datastores / Protocol Endpoints (PEs) do not show up in the Pure Storage dashboards or statistics (CSG-608)

The Pure Storage Management Pack does not show vVol datastores in the dashboards or report any statistics. 

Workaround: None

  • Management Pack Logs will not be available in vROps 8.1 (CSG-551)

While installing Pure Storage Management pack 3.0.0 on vROps 8.1 the following error message is displayed:

   State: Applied Adapter Post Script (Failed)
   Error: The PAK action "apply_adapter_post_script" script "$VMWARE_PYTHON_BIN postAdapters.py" failed

Due to this failure no logging from the Pure Storage Management Pack are available within vROps.

Workaround: None

  • "Adapter instance object has error status" reported in vROps when using virtual volumes (vVols) (CSG-623)

When virtual volumes (vVols) are being used on the Pure Storage FlashArray the vRealize Operations Manager (vROps) may trigger an alert stating: "Adapter instance object has error status".

This happens when vVols are quickly being destroyed or eradicated at the same time a vROps collection job is happening. The vROps management pack collects information about the vVol during the intial phase of the job but a short while later when referencing the object for additional metrics is no longer available and causes the adapter to crash, reporting "NullPointerException". This is often reported during vVol backup jobs.

Workaround: None