Dear community, I am trying to run the closed loop part of vFWCL use case in ONAP Beijing.
Currently, I am trying to update/add the policy. However, in this wiki ( https://wiki.onap.org/display/DW/Policy+on+OOM ) is suggested to first perfom a number of healthchecks to policy components. I can succeed in all of them with the exception of "Verify service name resolution is OK across policy components." *verify policy services connectivity* # pick any policy pod to run these tests from: # kubectl get pods --all-namespaces -o=wide kubectl exec -it dev-brmsgw-b877bc567-wbnbz -n onap -- bash -c "ping policydb" kubectl exec -it dev-brmsgw-b877bc567-wbnbz -n onap -- bash -c "ping pdp" kubectl exec -it dev-brmsgw-b877bc567-wbnbz -n onap -- bash -c "ping drools" kubectl exec -it dev-brmsgw-b877bc567-wbnbz -n onap -- bash -c "ping nexus" kubectl exec -it dev-brmsgw-b877bc567-wbnbz -n onap -- bash -c "ping message-router" In my particular case, from my brmsgw pod I can ping to policydb and pdp (that are ClusterIP types) but I can't ping to drools, nexus and message-router (that are NodePort types). From the wiki I mentioned before it is stated that: "It has been experienced in large OOM k8s multi-node full ONAP installations that components DNS and connectivity problems across pods through services. Eventually, the system becomes stable and ready to be used. Single node, smaller installations, do not seem to have these issues. Give the system enough time to make sure it has been initialized properly before pushing policies." I think this is exactly my issue since I have 2 physical nodes for ONAP and I can ping to the pod IP of drools, nexus and message-router but I can't through their services' IPs. E.g.: example: testing communication from brmsgw to drools ubuntu@rancher:~/oom/kubernetes$ kubectl exec -it onap-policy-brmsgw-576584b468-jcssv -n onap -- bash -c "ping -c 2 drools" PING drools.onap.svc.cluster.local (10.43.152.202) 56(84) bytes of data. ^C --- drools.onap.svc.cluster.local ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1009ms command terminated with exit code 1 ubuntu@rancher:~/oom/kubernetes$ kubectl exec -it onap-policy-brmsgw-576584b468-jcssv -n onap -- bash -c "ping -c 2 10.43.152.202" PING 10.43.152.202 (10.43.152.202) 56(84) bytes of data. ^C --- 10.43.152.202 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1008ms command terminated with exit code 1 ubuntu@rancher:~/oom/kubernetes$ kubectl exec -it onap-policy-brmsgw-576584b468-jcssv -n onap -- bash -c "ping -c 2 10.42.85.183" PING 10.42.85.183 (10.42.85.183) 56(84) bytes of data. 64 bytes from 10.42.85.183: icmp_seq=1 ttl=64 time=0.374 ms 64 bytes from 10.42.85.183: icmp_seq=2 ttl=64 time=0.069 ms --- 10.42.85.183 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.069/0.221/0.374/0.153 ms where 10.42.85.183 is the pod's IP of drools while 10.43.152.202 is the exposed service IP (NodePort). Does anyone knows how to debug this? Kind regards, Xoan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12074): https://lists.onap.org/g/onap-discuss/message/12074 Mute This Topic: https://lists.onap.org/mt/24974444/21656 Mute #usecaseui: https://lists.onap.org/mk?hashtag=usecaseui&subid=2740164 Mute #oom: https://lists.onap.org/mk?hashtag=oom&subid=2740164 Mute #policy: https://lists.onap.org/mk?hashtag=policy&subid=2740164 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
