nexus/knowledgebase/csd-wiki/ICSD/Upgrade-CMS-from-24.3-to-24.4_688996436.md

Upgrade-CMS-from-24.3-to-24.4_688996436

Pre-upgrade tasks

Because of this defect: Issue 2405372 - [SaaS]Customer startup fails due to having two references towards different repositories in Settings_LDAP_SETTING(ZA, PCS 1188476 )

Please run the following statement from JMX-Console, executeQuery(UCMDB:service=DAL services):

select * from urm_Resources where type='Settings_LDAP_SETTING' AND RESOURCE_ID !='ldap.setting.UCMDB'

If it returns any results, there are two options to follow next(either first or the second):

1. Delete the inconsistency in db: for each of the returned RESOURCE_ID, connect to the database and execute the below statement:

delete from urm_Resources where type='Settings_LDAP_SETTING' AND RESOURCE_ID ='resource_id_from_previous_output'

2. Add the param --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED in values.yaml before the upgrade process.

For ucmdbserver deployment at the of additionalOpts, like this example:

ucmdbserver:

deployment:

additionalOpts: -XX:HeapDumpPath=./runtime/log/java_heapdump.hprof --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED

database:

dbName: cms_ucmdb_db

schema: cms_ucmdb_schema

user: cms_ucmdb

jvmXmxMemory: 14336

Backup CMS before upgrade

Refer to the official CMS backup doc: https://docs.microfocus.com/doc/SMAX/24.3/CmsBackUpManagedK8S.

Perform CMS upgrade

Refer to the official CMS upgrade doc to do the following steps:

1. Download the new CMS charts package
2. Perform CMS version update
3. Troubleshooting: unable to access CMS UI after the upgrade

Post upgrade steps

The following steps are required because of the major version upgrade from Solr 8.x to Solr 9.x:

1. Run the following command to stop the Solr pod:

   kubectl scale deployment itom-ucmdb-solr -n <namespace> --replicas=0
   

2. Delete the data folder from the nfs: data-volume/ucmdb/solr/data file:
   1. Run the following command to navigate to the NFS path where the ucmdb persistent volumes are stored:

      cd <nfs_path>/data-volume/ucmdb/solr
      

      2. Run the following command to delete the data folder:

      sudo rm -rf data
      

3. Run the following command to start the Solr pod:

   kubectl scale deployment itom-ucmdb-solr -n <namespace> --replicas=1
   

4. Restart the UCMDB server:
   1. Run the following command:

      kubectl scale -n NAMESPACE --replicas=0 statefulset/itom-ucmdb
      

      2. Wait until both UCMDB pods (itom-ucmdb-0 and itom-ucmdb-1) are deleted, and then run the following command: kubectl scale -n NAMESPACE --replicas=2 statefulset/itom-ucmdb

How to check if reindex worked?

• Go to JMX-console under Topology Search Service and execute printStatusReportForAllCustomers:
• OK example(progress 100%):

• NOT OK example(see last result null):

If reindex was not run successful please use the below script to trigger the execution of reindex method from JMX for the entire farm(all customers):

1. get the script - contact Alin Zirbo

2.put the script and the jar on the cms efs at the path: cms_data_vol/ucmdb/server/conf/discovery/customer_1

3.cd to customer_1

4. chmod 775 *

5. chown 1999:1999 *

6. edit the sts of itom-ucmdb and add for JAVA_OPTS the next 3 lines

-Dcom.sun.management.jmxremote.port=29601 -Dcom.sun.management.jmxremote.authenticate=false

-Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=localhost

-Dcom.sun.management.jmxremote.rmi.port=29601

7.wait too be fully up

8.kubectl exec -it itom-ucmdb-1 -n cms -c itom-ucmdb -- /bin/bash -c "bash /ucmdb/conf/discovery/customer_1/status.sh reindex_all localhost"

9. check the results.txt from customer_1 folder (cat results.txt)

10. Share the results.txt from each farm with Diana Pop(dpop@ opentext.com)

cmdline-jmxclient-0.10.3-patched.jar

status.sh