ADCampus5.3 monitoring campus topology cannot be loaded normally

none

ADCampus5.3 monitoring campus topology cannot be loaded normally, error 502 is displayed

The topology shows 502. This problem will occur in the Campus E3311 version after a power failure and restart. The E3311P01 version has fixed this problem, and can be resolved by upgrading the version, or a temporary workaround can be adopted.

The pod to restart the topology is as follows

[root@uc00001 ~]# kubectl get pod -A | grep topology
campus              topology-be-deployment-6f6656d6dc-nlr4x       1/1     Running     0          16d
[root@uc00001 ~]# kubectl delete pod topology-be-deployment-6f6656d6dc-nlr4x -n campus
pod "topology-be-deployment-6f6656d6dc-nlr4x" deleted
[root@uc00001 ~]#
[root@uc00001 ~]# kubectl get pod -A | grep topology
campus              topology-be-deployment-6f6656d6dc-lsksk       1/1     Running     0          40s
[root@uc00001 ~]#  

This problem occurs probabilistically in the Campus E3311 version after a power failure and restart. If this problem occurs, restart the POD to recover it. It doesn"t matter if the server is not restarted