Loading...
Loading...
An error message may be displayed if an HPE Synergy Service Pack (SSP) hotfix is used to create a custom firmware bundle. However, the standard Synergy SSP will update as expected.When this issue occurs, the following error message(s) below may be displayed:"Image validation failed"AND"Image Compliance: host status is unknown"The system will be unable to deploy software via HPE and VMware vLCM Management stations.
Any ProLiant Rack and Tower servers with HPE Synergy hardware running VMware ESXi version 7.0 (or later) on a software appliance with the following configuration:HPE OneView for VMware vCenter (OV4VC) 11.0 (or later)VMware LifeCycle Manager (vLCM) 11.6VMware vCenter version 7.0 Update 3 - 8.0 (or later)HPE OneView for Synergy 6.50 - 9.20 (or later)
As a workaround, use the OV4VC/vLCM solution to deploy Synergy firmware together with the vSphere cluster image.Refrain from using a custom Synergy Service Pack (SSP), and instead, use the corresponding SSP that is listed inHPE Recommended VMware LifeCycle Manager Desired Image Definitionsavailable from HPE vibsdepot.If it is required, for any reason, to update to a newer firmware version on the Synergy compute node, use the other supported methods for a Synergy firmware upgrade.Note: Currently, HPE custom SSP configuration used with other HPE vendor tools (i.e., VMware vLCM and HPE OV4VC) arenotsupported. This HPE functionality is planned as a feature enhancement in a future release of HPE OneView.Document VersionRelease DateDetails3February 06, 2025Updated with additional versions in the Scope section that may be affected.2March 13, 2023Updated with additional OV4VC version that may be affected, such as version 11.0 or later.1July 15, 2022Original Document Release.
Operating Systems Affected:VMware ESXi 7.0
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.