Bug ID 1005049: DCD cluster stops working after adding a DCD or a standby BIG-IQ to a high availability configuration

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IQ AppIQ(all modules)

Known Affected Versions:
8.0.0

Fixed In:
8.0.0.1

Opened: Mar 24, 2021

Severity: 3-Major

Symptoms

After adding a standby BIG-IQ to a high availability (HA) configuration or while (less likely) adding a DCD, the DCD cluster no longer functions and the restjavad.0.logs shows a message similar to the following: [HTTP/1.1 503 Service Unavailable] Open Distro not initialized

Impact

BIG-IQ is unable to receive new analytics statistics and events and cannot display existing events.

Conditions

Adding a standby BIG-IQ in a high availability (HA) configuration, or (less likely) when adding a DCD.

Workaround

After adding the standby BIG-IQ for a high availability (HA) configuration, or a DCD, run the following command on the active BIG-IQ: export JAVA_HOME=/usr/lib/jvm/jre-1.8.0-openjdk.x86_64 ; /bin/bash -c "/usr/share/elasticsearch/plugins/opendistro_security/tools/securityadmin.sh -h `netstat -nap | grep ':9300 ' | grep LISTEN | awk '{print $4}' | rev | cut -c 6- | rev` --accept-red-cluster -cd /var/config/appiq/elasticsearch/utils/ -icl -nhnv -cacert /var/config/rest/elasticsearch/config/es_root-ca.pem -cert /var/config/rest/elasticsearch/config/es_admin.pem -key /var/config/rest/elasticsearch/config/es_admin-key.pem"

Fix Information

This issue is fixed and DCD clusters work as expected after adding a standby BIG-IQ or a DCD.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips