Loading...
Loading...
The deployment of SPP 2024.04.00.01 (or later) may not start when initiated from a remote system running Linux and using a passphrase-protected SSH key. This issue occurs when using SUM versions 10.8.0 through 11.2.0.This issue affects both Command Line Interface (CLI) deployments (using an input file) and Graphical User Interface (GUI) deployments.When this issue occurs, the deployment process will terminate with one of the following errors:Connection failure to remote node - UNKNOWN with return code 4.Incorrect passphrase or private key, or incorrect sudoers settings on the remote node.Error: General failure occurred, or user cancelled the update.
In the scenario described above, any HPE systems running Linux and HPE SUM versions 10.8.0 through 11.2.0.
To avoid this issue, update SUM to version12.0.0(or later).As a workaround, perform any of the following:Linux-based hostIf the updates must be performed from a Linux-based host, use either of the following options:In inputfile, use parameters UID and PWD (username and password) instead of a passphrase.ORIn inputfile, use UID, PWD, and DELETEINPUTFILE. The DELETEINPUTFILE parameter instructs SUM to delete the input file after it has been read.Windows-based hostThe SPP may be deployed from a remote Windows-based host, and will not experience this issue.SUM version 10.7.0Use SUM v10.7.0 to customize the SPP with the required components:Select signed rpm files from SPP 2024.09.00.00.Select fwpkg files from SPP 2024.09.00.00, or 2024.11.00.00.Use this custom SPP to update the system.Revision HistoryDocument VersionRelease DateDetails2April 28, 2025The Resolution section has been updated with the software version containing the solution.1February 11, 2025Original Document Release.
Operating Systems Affected:Not Applicable
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.