This article focusses on checks to be carried out when if contrail web UI is not accessible.
Contrail Web UI not accessible.
If incase of HA deployment which is most the case, all the traffic to Web UI containers are forwarded via HAproxy VIP
If Web UI is not accessible, continue with below check list
1. Check if Web UI containers are Up and Running in all three controller nodes.
[root@aio-controller-1 ~]# docker ps | grep -i web 4fe83ae6a246 enterprise-hub.juniper.net/contrail-container-prod/contrail-controller-webui-web:21.4.L2.329 "/entrypoint.sh /usr…" 15 months ago Up 8 months webui_web_1 db0bb49cc1b8 enterprise-hub.juniper.net/contrail-container-prod/contrail-controller-webui-job:21.4.L2.329 "/entrypoint.sh /usr…" 15 months ago Up 8 months webui_job_1
2. Check if haproxy and keepalived containers are Up and Running.
[root@aio-controller-1 ~]# docker ps -a | egrep "haproxy|keepalive" e3ce3058b4ed registry-docker-local/kolla/centos-binary-keepalived:queens "dumb-init --single-…" 15 months ago Up 11 seconds keepalived 5e5a9bc654f8 registry-docker-local/kolla/centos-binary-haproxy:queens "dumb-init --single-…" 15 months ago Up 7 seconds haproxy
3. Check if you are able to access the web UI using individual IP of controllers.
4. If point 3 works, then containers are healthy as per point 2, check logs of keepalived and haproxy container.
#### To check haproxy logs [root@aio-controller-1 ~]# docker logs --tail 10 -f haproxy #### To check keepalived logs [root@aio-controller-1 ~]# docker logs --tail 10 -f keepalived
5. If point 3 does not work, check for logs of web ui container.
[root@aio-controller-1 ~]# docker logs --tail 10 -f webui_web_1
If we are not receiving hits as per logs in web ui container , check for any network issues in the host level or in the network. Contact Juniper Support if required.