Hotfix for 5.0.x.x Upgrade to 6.0.0.0 and Increased file size support for Update UI artifact

Hotfix - Increased file size support for Update UI artifact and 5.0.x.x Upgrade to 6.0.0.0

Issue Description:

 This document helps with resolution of two issues:

          1. SRM vAPP upgrade from versions less than 5.0.2.2 to version 5.1.1.0 will fail to upload the Update-UI.zip file with error "An unknown error encountered while uploading the file. It may have reached the maximum file size allowed. Please check the server logs for more details."

          2. It was observed that SRM vAPP upgrade from any of the SRM/SMR 5.0.x.x versions (5.0.0.0, 5.0.1.0, 5.0.2.0, 5.0.2.1, 5.0.2.2) is getting stuck due to the communication error observed between webservice-gateway service which is preventing the upgrade process to continue further.

Summary :

Issue 1:

SRM vAPP upgrade from versions less than 5.0.2.2 to version 5.1.1.0 will fail to upload the Update-UI.zip file with error "An unknown error encountered while uploading the file. It may have reached the maximum file size allowed. Please check the server logs for more details.."

Due to the SLES 15 SP6 changes, file size of SRM_x.x.x.x_vApp_Update_UI.zip has been increased and upload of Update-UI.zip will fail.

Notes
Note:
  1. Issue is observed only in SRM vAPP

  1. Impacted SRM versions are 4.10.0.0, 4.10.0.1, 4.10.0.2, 4.10.0.3, 5.0.0.0, 5.0.1.0, 5.0.2.0, 5.0.2.1 

Resolution :

Before upgrading to SRM 5.1.1.0 and from any of these SRM versions 4.10.0.0, 4.10.0.1, 4.10.0.2, 4.10.0.3, 5.0.0.0, 5.0.1.0, 5.0.2.0, 5.0.2.1 below workaround steps need to be executed.

Steps :

  1. Place the respective centralized management package version to ‘< SRM Install directory> /Tools/Module-Repository folder’ in SRM Frontend VM
  2. Run below command
  3. manage-modules.sh update centralized-management
  4. Restart tomcat service


Hotfix Package :

The hotfix package is different for impacted SRM versions.

SRM SRM 4.10.0.0, 4.10.0.1, 4.10.0.2, 4.10.0.3 and 5.0.0.0 centralized-management-8.0.0u1-linux-x64.pkg

SRM 5.0.1.0 & 5.0.2.0 centralized-management-8.0.2u1-linux-x64.pkg

SRM 5.0.2.1 centralized-management-8.0.2u2-linux-x64.pkg

     

Issue 2:

SRM/SMR 5.0.x.x upgrade to 6.0.0.0 gets stuck

Due to the communication error observed between webservice-gateway service which is preventing the upgrade process to continue further.

Resolution :

Before upgrading to SRM 6.0.0.0 from any of the SRM versions 5.0.0.0, 5.0.1.0, 5.0.2.0, 5.0.2.1, 5.0.2.2 below workaround steps needs to be executed.

Steps :

  1. Place the respective centralized management package version to ‘< SRM Install directory> /Tools/Module-Repository folder’ in SRM Frontend VM
  2. Run below command
  3. manage-modules.sh update centralized-management
  4. Restart tomcat service

Hotfix Package :

The hotfix package is different for impacted SRM versions.

SRM 5.0.0.0 centralized-management-8.0.0u1-linux-x64.pkg

SRM 5.0.1.0 & 5.0.2.0 centralized-management-8.0.2u1-linux-x64.pkg

SRM 5.0.2.1 centralized-management-8.0.2u2-linux-x64.pkg

SRM 5.0.2.2 centralized-management-8.0.2u3-linux-x64.pkg

Please find the below links to access the packages:

Notes
Note:
The upgrade stuck issue from 5.0.x.x to 6.0.0.0 is also observed with SMR and the same hotfix package needs to applied for corresponding SMR versions.






    • Related Articles

    • SRM 6.1.0.0 - Stored Report Hotfix

      Issue Description: After the SRM upgrade that included Java 17, previously stored report files serialized using older Java versions fail during deserialization. This occurs due to incompatibilities introduced by changes in Java’s ...

    • SRM vApp External Automated Upgrade Script

      Overview This script automates the SRM update process for vApp environments. It supports both All-in-One (AIO) and Distributed deployments. Important Notes Windows SRM environments are not updated by this script they are skipped and must be handled ...

    • SRM/SMR- 6.1.0.0 | Device Discovery status to be retained post 6.1.0.0 upgrade

      Symptoms Device discovery status greyed out post upgrade to SRM and SMR 6.1.0.0 environment. Cause Discovery status results are stored in h2 database. h2 database has been upgraded from version 2.1.x to 2.4.x in 6.1.0.0 release as the older version ...

    • SRM Linux External Automated Upgrade Script

      Overview This script automates the update process for SRM binary linux platforms, including RHEL and SLES. It supports both All-in-One (AIO) and Distributed environments. Important Notes Windows SRM environments are not updated by this script; they ...

    • SRM 6.0.0.2 - Hotfix for Powerstore Collector Issue

      Issue Description: Any upgrade to SRM 6.0.0.2 with Power Solution Pack, the PowerStorecollector stopped collecting data due to runtime errors (NoClassDefFoundError). Summary: SRM 6.0.0.2 includes older versions of key libraries, specifically ...