Pega Application URL is not Reachable but the Application PODS were UP and Running fine

General
, , , , , , ,
1

It’s found that, During the Application Code Migration and Cleanup activity (Not sure what happened), Application URL went unreachable but found that All the Application PODS were up and running in Healthy Mode.

Any advice on how to fix the issue?

2

Root Cause: Found that, Required Access-Group (Un-authenticated One) removed by mistake.

Solution Applied to fix the Issue:

  1. Even though, Custom Application created for Client on top of PRPC layer and Custom Application Un-authenticated Access group is deleted, Default Un-authenticated Access-group remains in the system.

  2. To Enable that PRPC:Un-Authenticated Access group, need to point the system name from Custom Application to Default PRPC System Name: pega to fix the issue.

  3. Since OpenShift is accessible, From the OpenShift configmap, injected the below prconfig setting to re-point the system name from Current Custom Application layer to Default PRPC one.

  1. Performed the web pods rollover restart upon the above setting added in the Openshift Configmap On-the-Fly Deployment.

  2. Application URL became accessible post the new pods came up.

  3. LSA imported the deleted access group.

  4. No Issues were found so removed the below setting from OpenShift Configmap and performed the Web user pods rollover restart to let the System Name Point out to Custom Application Layer one which was built on top of PRPC one.