TML5.3.1HF2 - CM components keep switching between RESOLVED and STANDBY
If the password has been changed previously and the cluster has been restarted then the cm pod starts changing from RESOLVED to STANDBY and if Config Manager is not starting

NA

If the password has been changed previously and the cluster has been restarted then the cm pod starts switching from RESOLVED to STANDBY


Check the secret papi_property using the following command:

kubectl  get secrets papi-property -o yaml

Copy the content and decode it using any decoder application like base 64.

if you have changed the password for the portal and the secret is still showing the old password then follow the below steps:

1. Edit the Secret and modify the passowrd.

2. Encode the secret and paste it to the papi-property secret.

3. Go to the manifest directory and open tml_papi_properties.json file.

4. Add the 'Password' attribute with the new password as a value 

5. Undeploy and deploy the cm pod.

Wait for a few minutes to see the CM pod Active.

CM-components-keeps-switching-between-RESOLVED-and-STANDBY-Changed-password-GUI-is-not-coming-up