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.
Note:
- Issue is observed only in SRM vAPP
- 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 :
- Place the respective centralized management package version to ‘< SRM Install directory> /Tools/Module-Repository folder’ in SRM Frontend VM
- Run below command
- manage-modules.sh update centralized-management
- 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 :
- Place the respective centralized management package version
to ‘< SRM Install directory> /Tools/Module-Repository folder’ in SRM Frontend
VM
- Run below command
- manage-modules.sh
update centralized-management
- 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
Please find the below links to access the packages:
Issue 1: SRM_Hotfix_5.0.x.xIssue 2: SRM_Hotfix_6.0.0.0
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
ViPR SRM Windows binary 5.x: Backend services may fail to start automatically
Summary: Backend services may fail to start automatically due to elongated start-up times of the MySQL service. Add the mysql service as a dependency to the APGBackendApg1 service to fix the issue. Detailed Article Symptoms: The Backend (apg) service ...HCLSRM - Automation for Increasing Boot Partition Size by Migrating to a New Partition
Detailed Article Pre-Requisite: "In the vSphere client, provision an additional disk of at least 1 GB for each SRM VM that requires increased boot space." Symptoms Legacy SRM installations, such as those starting from SRM 3.x and subsequently ...SRM 6.0.0.0 | Automated Script to Copy MYSQL libraries to System Directories and Copy apg-services script file to systemd
Summary : This script will copy the required MySQL Libraries and apg-services script file to System directories for SRM/SMR Binary Linux ( RHEL and SUSE ) deployments . The script should be executed at SRM/SMR Pre-upgrade level. Steps to Execute the ...SRM 5.x :: How do I configure SRM to change authentication from LDAP to LDAPS
Summary: What are the steps to configure SRM to change the authentication from LDAP to LDAPS Detailed Article Instructions Below are the steps to configure SRM to change the authentication from LDAP to LDAPS over SSL port 636 1. Log in to the SRM ...SRM 6.0.0.0 | CIAM Environment Setup Configuration for Single sign-on (SSO)
Summary: Steps to generate a secret key and configure the CIAM server environment for Linux (vApp and Binary) and Windows Binary SRM deployments. Instructions Follow the steps below on the SRM Frontend CLI/PuTTY to configure and start the CIAM ...