IBM Support

RabbitMQ pods repeatedly restart on an Automation Document Processing ROKS deployment

Troubleshooting


Problem

When Automation Document Processing is deployed in a Red Hat OpenShift Kubernetes (ROKS) environment, the RabbitMQ pods repeatedly restart.

Cause

RabbitMQ pods are given thirty minutes to come up in a ready state before a restart is triggered.  For a large deployment, such as a Cloud Pak for Automation (CP4A) deployment in ROKS with multiple CP4A components, thirty minutes might not be a sufficiently long time for RabbitMQ to deploy.

Environment

Specific to Cloud Pak for Business Automation version 20.0.3

Resolving The Problem

Add a retries value in the ca_configuration section in the cr yaml.  Set the value to 150, which replaces the default value of 100.
 
ca_configuration:
  global:
    retries: "150"

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m3p000000hAKPAA2","label":"Operate-\u003EADP Install\\Upgrade\\Setup"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
07 February 2023

UID

ibm16379934