Unable to access Impact UI after failback
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.
ProblemAfter 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.
CauseWhen an Impact failback happens, the Impact UI is not able to identify which is the active primary cluster.
ResolutionDelete all Netcool/Impact server pods by using the example command:
There is downtime while the Netcool/Impact servers are being restarted. When
<release>-nciserver-0 is running again, the Netcool/Impact UI is available.
oc delete pod <release>-nciserver-0 <release>-nciserver-1 ... <release>-nciserver-n