No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


DB Node Capacity Expansion Failed After a FusionManager Rollback

Publication Date:  2014-07-15 Views:  110 Downloads:  0
Issue Description
 FusionManager is upgraded from V100R003C10SPC300 to V100R003C10SPC500 and then rolled back to V100R003C10SPC300. A user, then, expands the capacity of the FusionCube database (DB) node. However, the capacity expansion fails, and the information indicating failure in installing FusionStorage Agent is displayed in the log.
 Then, we use PuTTY and the floating IP address to log in to the FusionManager node to check the /var/log/GalaxManager/irm/common/ irm_common.log file generated when the failure occurs. The following information is displayed in the file.
Alarm Information
Handling Process
1. Log in to the FusionManager portal, choose Resources > Template > ISO, and delete the ISO file used during the capacity expansion.
2. Upload the installation source file that uses the new password, and use the included ISO file to expand the capacity of the FusionCube DB node again.
Root Cause
 After FusionManager is upgraded from V100R003C10SPC300 to V100R003C10SPC500, the passwords of users root and galaxmanager are changed to new passwords.
 However, when FusionManager is rolled back, passwords of users root and galaxmanager are not changed and they still use the new passwords. During the capacity expansion, the FusionStorage Manager node uses the old passwords when installing FusionStorage Agent nodes on Computing Node Agent (CNA) nodes. The passwords in the installation source file and those used by the FusionStorage Manager node are inconsistent. As a result, the capacity expansion fails