5.3.3 Release Notes

General

Version 5.3.3 of the Everpure vSphere HTML Client Plugin supports vSphere (vCenter and ESXi) version 6.7U3 and later and Purity version 6.1.x and later.

Users can upgrade to this version of the plugin via deploying the Everpure VMware Appliance. This version is certified by VMware.

What’s New

• Starting in vSphere 8.0, VMware no longer supports local plugins to be installed in vCenter (Everpure vSphere Plugin versions 4.5.2 and below). Please use the remote versions of Everpure's vSphere plugin (Everpure vSphere Plugin versions 5.0.0 and above). For more information please refer to this VMware KB.
• This version of the plugin uses the VMware Remote Plugin Architecture
  • More information on the VMware Remote Plugin Architecture can be found here.
  • More information on why Everpure is using this can be found Why Everpure is Deprecating the Local vSphere Plugin in Favor of the Remote vSphere Plugin.
• Release notes for Everpure's VMware Appliance (OVA) can be found at Everpure VMware Appliance Release Notes. Everpure's remote vSphere plugin can be updated independently of the appliance. The VMware appliance can be Everpure VMware Appliance Quick Reference .
  • When the OVA's operating system needs to be updated, the OVA will need to be upgraded first in order to see the remote vSphere plugin upgrade options. When running puresw list if your target version vSphere plugin version is not visible but the OVA says it can be upgraded, upgrade the OVA first.

Fixed issues

• TMAN-19491: Edit datastore dialog won't completely load and the "loading vmfs datastore information" status is displayed. This has been fixed.
• TMAN-19482: Security fixes and hardening
  • CVE-2023-20860
  • CVE 2023-20883
  • CVE-2022-25857
  • CVE-2022-38749

Known issues

• If an array's management ports were accessible upon adding the array to the vSphere plugin and later became inaccessible, loading certain windows in the vSphere plugin might take greater than 10 minutes. To workaround this issue there are currently two options:
  1. Wait until the array list populates in the vSphere plugin screen and remove the inaccessible array
  2. If the vSphere environment has only had Pure's remote plugin installed, un-registering the plugin and registering it again should clear out the array connections that existed and the existing accessible arrays can be added back
  • Pure is currently evaluating options to improve this situation in TMAN-19146