KB: Install customization-ready container fails with timeout.

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

#########################################################################
# Running: 100-after-server-processes-ready for provision
#########################################################################
Calling ./000_add_client0_user.groovy as a Groovy script.
Trying to log in as User 'UC/UC'
Trying to log in as User 'ADMIN/ADMIN'
Caught: com.uc4.communication.TimeoutException: Request timed out (300000)
com.uc4.communication.TimeoutException: Request timed out (300000)

Environment

Product: Automic Automation Kubernetes Edition

Version: 24.4.X

Cause

 

• Running an upgrade (a regular upgrade, not ZDU) from a previously successfully installed version; however, the state of the installation is not reflected in the automic-automation ConfigMap.

• Running a new installation, but the install customization pod died and had to be restarted after it disabled the UC/UC user.

Resolution

This will be fixed in a future release.

NOTE: In the automic-automation ConfigMap, the statusVersion should be the last installed version (without the hf numbers) and statusState should be provisioned.

If this is not the case, and the actual upgrade has not yet run, do the following:

1. Scale down the install-operator to 0.

2. Edit the automic-automation ConfigMap and set the statusVersion to match the specVersion, and the statusState to be provisioned.

3. Run helm upgrade (you do not need to scale back up the install-operator before that).

If this happened after the upgrade (non-ZDU upgrade only!):

1. Scale down the install-operator to 0.

2. Edit the automic-automation ConfigMap and set the statusVersion to be the version before the upgrade (the specVersion). Edit the statusState to be provisioned.

3. Run helm upgrade (you do not need to scale back up the install-operator before that). This will shut down the system, re-run dbload, recreate the deployments, and run the customizations in upgrade mode.

NOTE: After any installation/upgrade, check that the statusState is provisioned and the statusVersion matches the expected specVersion. This signals that the install-operator has successfully performed its full workflow of the AE installation on the K8s environment.

Additional Information

Defect ID: DE180722