When installing portal 5.2 ınstallation failed on dispatcher healthcheck
search cancel

When installing portal 5.2 ınstallation failed on dispatcher healthcheck

book

Article ID: 268944

calendar_today

Updated On:

Products

CA API Developer Portal

Issue/Introduction

While we are trying to install 5.2 version developer portal to a cluster, We  getting some error for dispatcher pod, it returns like below error.

This may even be observed in a existing deployment as IPs change.

[error] 64#64: *32 access forbidden by rule, client: XX.XX.X.X, server: _, request: "GET /nginx_status HTTP/1.1", host: "xxx.xx.x.xxx:8443"
"GET /nginx_status HTTP/1.1" 403 243 0.000

When we try to nginx_status with curl localhost it returns "http 200 ok", but when we call it with pod IP it returns "403 access forbidden" error.  

Due to this the healtcheck and liveness probe fails and the pod is failing 

Environment

Release : 5.2

Resolution

On Openshift you may need to add  the IP list for the Healthcheck and Liveness  probe manual. 

you need to configure the allowed  PROBE IP RANGE on openshift by adding the following line in the values.yaml file.

dispatcher:
  additionalEnv:
  ## Add whitelist IP Range for Dispatcher
  PROBE_IP_RANGE: xxx.xxx.xxx.xxx/16