Operational Defect Database
BugZero found this defect 105 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Hewlett Packard Enterprise | a00137641en_us
Advisory: HPE 3PAR StoreServ Storage - Upgrading to HPE 3PAR OS 3.3.2 EMU1 Might Cause a Service Disruption if Duplicate Key Values for a VMware Virtual Volume (vVOL) are Present During VASA Migration
Last update date:
2/12/2024
Affected products:
HPE 3PAR StoreServ 20000 Storage
HPE 3PAR StoreServ 8000 Storage
HPE 3PAR StoreServ 9000 Storage
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
When there are VMware Virtual Volumes (vVOLs) with multiple unnecessary and incorrect duplicate key entries with the name VP-IN-hostuuid and VP-IN-hostwwn in the vVOL configuration, vSphere APIs for Storage Awareness (VASA) migration can sometimes fail after an update to HPE 3PAR OS 3.3.2 EMU1. These multiple key entries for a vVOL can cause a very large (and unexpected) memory allocation during an upgrade to HPE 3PAR OS 3.3.2 EMU1 with VASA migration that may cause vVOLs to become unavailable.
Scope
This issue is applicable to any pre-HPE 3PAR OS 3.3.2 EMU1 release while upgrading to HPE 3PAR OS 3.3.2 when vVOLs are in use.
Resolution
This advisory will be updated as a resolution becomes available. As a workaround, contact HPE Support to determine if duplicate key values are present. If duplicate keys are present, HPE Support will clear the duplicate keys in the vVOL configuration. This must be done before upgrading to HPE 3PAR OS 3.3.2 EMU1. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Support Alerts. Sign up for Support Alerts at the following URL: HPE Email Preference Center
