Unable to access Impact UI after failback

Edit online

Following Netcool®/Impact failback, you are not able to access the Impact UI. This happens because following failback, the Impact UI is not able to identify which is the active primary cluster.

Problem

After Netcool/Impact failback, you are not able to access the Impact UI, and the following error is displayed:

Connection Failed: Unable to contact the selected cluster. The primary cluster member may be down or has been switched.

Cause

When an Impact failback happens, the Impact UI is not able to identify which is the active primary cluster.

Resolution

Delete all Netcool/Impact server pods by using the example command:

oc delete pod <release>-nciserver-0 <release>-nciserver-1 ... <release>-nciserver-n

There is downtime while the Netcool/Impact servers are being restarted. When <release>-nciserver-0 is running again, the Netcool/Impact UI is available.

Draft comment: LOUISERoberts
#2789