OPenshift 3.11 Container Gatway v10 not starting

Products

• CA API Gateway
• API SECURITY
• CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7)
• CA API Gateway Enterprise Service Manager (Layer 7)
• STARTER PACK-7
• CA Microgateway

Issue/Introduction

OPenshift 3.11 Container not starting

unhealthy : Liveness probe failed: info: No menu in node `(dir)Top'. date: /opt/SecureSpan/Gateway/node/default/var/started: No such file or directory expr: syntax error /opt/docker/rc.d/diagnostic/health_check/base.sh: line 4: [: : integer expression expected…

22 times in the last 21 minutes

unhealthy : Readiness probe failed: info: No menu in node `(dir)Top'. date: /opt/SecureSpan/Gateway/node/default/var/started: No such file or directory expr: syntax error /opt/docker/rc.d/diagnostic/health_check/base.sh: line 4: [: : integer expression expected

27 times in the last 21 minutes

Environment

Release : 9.4

Component : API GATEWAY

Cause

very low resources to start the container was defined at container-gateway.yml 

Resolution

1. The Default values contained in container-gateway.yml are the following :

     containers:
     - name: gateway-container
     image: "${DOCKER_IMAGE_NAME}:${DOCKER_IMAGE_TAG}"
     imagePullPolicy: Always
     resources:
     requests:
     cpu: 4000m
     memory: 6Gi
     limits:
     cpu: 4000m
     memory: 6Gi

2. Customer modified to the original values to following  :

containers:
  - name: gateway-container
  image: "${DOCKER_IMAGE_NAME}:${DOCKER_IMAGE_TAG}"
  imagePullPolicy: Always
  resources:
  requests:
  cpu: 1
  memory: 2Gi
  limits:
  cpu: 2
  memory: 2Gi

3.  Support tested with more higher values at container-gateway.yml and started working.

Tested with new Values and worked  :
 cpu: 1000m
 memory: 4Gi
 limits:
 cpu: 1000m
 memory: 4Gi

Note : the values tested are not intended for a production environment, this is an example for test purposes only