Troubleshooting deployment issues



Deployment manager failed

Scope

This occurs of because of network issues.

Workaround

Perform the following steps:

  1. Run the following command:
    helm ls --all -n <namespace> | grep pending-install
    helm delete <each of the service in previous step> -n <namespace>
  2. Run the installer again by using the following command:
    ./deployment-manager.sh


Deployment manager failed with a bad decrypt message

Scope

This issue occurs because of an incorrect encryption password entered during deployment. The following error appears:

bad_decrypt_error.png

Workaround:

Run the deployment again with the correct encryption password. 

For information about the encryption password, see Preparing-for-password-encryption.


Service deployment failed

If the deployment for any service fails, run the following command:

helm ls --all -n <namespace> | grep -I fail

Also, zip and share the logs folder with BMC.


Tenant entry is not added for the BMC Intelligent Integrations database

To resolve this issue, update the PostgreSQL database with the following command:

./commons/run_sql_query.sh


The installation aborts because of an RSSO error

Scope

The rsso-pod-dbinit pod displays an error and installation aborts.

Workaround

Perform the following steps:

  1. Run the following command:

    ~]# helm delete rsso -n <namespace>
  2. Delete the PostgreSQL pods and wait for the pods to be up and running again. Run the following command to delete the pods:

    ~]# kubectl delete pod postgres-postgresql-ha-postgresql-0 postgres-postgresql-ha-postgresql-1 -n <namespace> --force --grace-period=0

    ~]# kubectl exec -it postgres-bmc-pg-ha-0 bash -n <namespace>

    bash-5.1# PGPASSWORD=pGTest2020 psql -h postgres-postgresql-ha-postgresql  -p 5432 -U postgres -d postgres

    postgres=# drop database ade_rsso;
  3. Rerun the installer.


The Redis HAProxy pods run into CrashLoopBackOff

Scope

This issue occurs while installing BMC Helix IT Operations Management.

The following error is displayed:

Error: client rate limiter Wait returned an error: context deadline exceeded
[240220-152157] ERROR: Failed to install helm chart: redis.


Workaround

On every node of the cluster, run the following command:

sed -i 's/LimitNOFILE=infinity/LimitNOFILE=65535/' /usr/lib/systemd/system/containerd.service
systemctl daemon-reload
systemctl restart containerd

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*