Mashery Local 5.3 Uploading the Certificate or keystore from Jenkins console and CM, TM pods in STANBY state error.

Mashery Local 5.3 Uploading the Certificate or keystore from Jenkins console and CM, TM pods in STANBY state error.

book

Article ID: KB0075504

calendar_today

Updated On:

Products Versions
TIBCO Cloud API Management - Local Edition ML 5.3.0 HF1, ML 5.3.0

Description

Scenario:

Uploading the server key certificate or the server keystore for traffic manager and configuration manager from Jenkins console using the 4 options available on the deploy tab.

Error:

The CM, TM pods stay in STANDBY state.

Health check up fails with an error as below:

{"tag":"tml-tm.tmdata","ingestion_time":"","HOSTNAME":"tm-deploy","process":"containeragent","function":"containeragent","TML_CLUSTER_NAME":"Tibco Mashery Local Reference Cluster","TML_ZONE_NAME":"local","POD_IP":"","message":"[ERROR] [LifecycleServicesWorkerThread] c.m.t.c.a.i.s.ProxyContainerServiceImpl - Health ping error - GET request to http://127.0.0.1:80/mashping failed; Reason: Failed to connect to /127.0.0.1:80","LOG_FORMAT_VERSION":"1.0"}

Resolution

Resolution:

Please check for the missing comma after the fields below and add the commas after the fields

tm_keystore_password": "xqwfgh", in  tml_tm_properties.json
"cm_keystore_password": "ewdghsj3", in tml_cm_properties.json

If the pods are already deployed then we will have to un-deploy and redeploy the pods using scripts available in the manifest folder

./undeploy-cm-pod.sh
./deploy-cm-pod.sh
./undeploy-tm-pod.sh
./deploy-tm-pod.sh

Issue/Introduction

Mashery Local 5.3HF1 after Uploading the Certificate/keystore from Jenkins console the CM, TM pods are in STANDBY State