LI81493: ANALYTICS OPERATOR POD RESTARTS MULTIPLE TIMES IN APIC DEPLOYMENT ON CLOUD PAK FOR INTEGRATION

APAR status

• Closed as program error.

Error description

• Analytics operator pod in API connect deployment on Cloud Pak
  for Integration restarts multiple times after upgrade to API
  Connect fix pack 10 (2018.4.1.10) in Cloud Pak for Integration
  version 2020.1
  

Local fix

• A local workaround is to increase a readiness and liveness
  timeout from 1 seconds to 10 seconds.
  
  On a machine with kubectl access that has access to analytics
  subsystem, locate the analytics namespace for use below.
  Execute kubectl get deployments -n <ns> , local analytics
  operator pod.
  kubectl edit deployment <release>-analytics-operator -n <ns>
  Modify the livelinessProbe and readinessProbe sections, increase
  timeoutSeconds to 10
            exec:
              command:
              - /aop
              - health
            failureThreshold: 3
            initialDelaySeconds: 120
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
  The operator pod should restart on it's own.
  

Problem summary

• Analytics Operator pod may restart multiple times or may fail to
  start with "CrashLoopBackOff"  This problem will prevent
  analytics backup and restore operations from working.
  

Problem conclusion

• The issue is fixed in v2018.4.1.11
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels

• R18X PSY

     UP