Operational Defect Database
BugZero found this defect 63 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Hewlett Packard Enterprise | a00138416en_us
Advisory: HPE B-Series Switch - HPE SANnav Deployments That Have Customized SANnav Docker Home Path Configured To A Value Other Than The Default Path Of "/var/lib" Will Be Unable To Upgrade To SANnav Version 2.3.1
Last update date:
3/18/2024
Affected products:
HPE Storage SANnav Management Software
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
Migrations from HPE SANnav versions 2.2.2x or 2.3.0 to version 2.3.1 fail when at least one of the following conditions are encountered: In SANnav versions prior to v2.2.1, SANnav docker home path was customized to something other than the default path of "/var/lib", later upgraded to versions 2.2.1, 2.2.2x, or 2.3.0 with this customized path, and then migration to version 2.3.1 was attempted. Backup from a SANnav server having a different docker home path than the current SANnav server is restored and migration to version 2.3.1 is attempted (for example, backup from an OVA) which has a default docker home path) is restored on a server with custom docker home path. NOTE : This issue only applies if the SANnav docker home path (/var/lib) was customized before attempting migration to version 2.3.1, and the symptoms below will be seen. Migration from SANnav versions 2.2.2x or 2.3.0 to version 2.3.1 hangs with the following error logged in the install log file: SANnav Management Portal log file name : <SANnav Home>/Portal_2.3.1_bld182/logs/install-sannav-<timestamp>.log SANnav Global View log file name : <SANnav Home>/Global_2.3.1_bld182/logs/install-sannav-<timestamp>.log Error printed in above mentioned applicable log file : "Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again."
Scope
This advisory applies to the following HPE SANnav deployments on HPE B-series switches: HPE SANnav Management Portal version 2.3.1 HPE SANnav Global View version 2.3.1
Resolution
This issue will be fixed in a future HPE SANnav software release. Until then the workaround will need to be followed. If the upgrade and migration to the HPE SANnav version that contains the software update was already attempted and failed, then recover the server back to the previous working version and follow these steps: Uninstall HPE SANnav version 2.3.1. Uninstall the previous version of HPE SANnav. Reinstall the previous version of HPE SANnav. Restore the backup. Follow the steps in the workaround section. Workaround Before attempting an upgrade and migration to HPE SANnav version 2.3.1, follow the steps below: Stop the HPE SANnav server. Edit the configuration file to set the docker home path to the customized docker home path location: SANnav Management Portal Configuration File to edit : <SANnav Home>/Portal_<version>_<bldXXX>/conf/server.properties SANnav Global View Configuration File to edit : <SANnav Home>/Global_<version>_<bldXXX>/conf/server.properties Property to edit : sannav.docker.home.dir For example: Change /var/lib in "sannav.docker.home.dir=/var/lib” to your customized docker home path such as “sannav.docker.home.dir=/home/sannav" Restart the HPE SANnav server. How to find current customized docker home location? Run the following command: cat /etc/docker/daemon.json | grep data-root Sample output: "data-root" : "/home/sannav/docker" Use the path up to (but not including) the "docker" directory. For example, in this case, the customized docker home location is "/home/sannav". This document will be updated when more information is available. 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
