ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SV-Readiness n liveliness probe to the VSE docker image is resulting in restarts

book

Article ID: 186694

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction


We need to add Readiness and liveliness probe as its mandated for container health check in openshift.

When we tried to add Readiness or liveness to the containers its continuously restarting . When we removed the VSE didn't restart.

We tried all the options for readiness  HTTP/TCP/COMMAND

COMMAND Readiness probe :


readinessProbe:         

          exec:

            command:

            - '[ -d /devtest/vseDeploy/${OCP_APP_NAME}_2013/ ]'

          initialDelaySeconds: 180

          periodSeconds: 5  

  HTTP Readiness:

readinessProbe:

          failureThreshold: 10

          httpGet:

            path: <VSE Monitor url>

            port: 1505

            scheme: HTTPS         

          initialDelaySeconds: 60

          periodSeconds: 10

          successThreshold: 1

          timeoutSeconds: 5

TCP Readiness:

readinessProbe

            tcpSocket:

        port: 2013

      initialDelaySeconds: 180

      periodSeconds: 10

Cause

Configuration issue

Environment

Release : 10.5

Component : CA Service Virtualization

Resolution

Use the <pod_ip> instead of the Host name (OCP_APP_NAME). This fixed the 404 and the readiness probe issues.