1
0
-1
1 answer
- 10-1
This is the service's floating IP that is in the pending state. This could be due to your Cloud Client not having any available IP's to give to the Portal Service. Although I have seen services hang in the pending state for no reason before, if you know there re available floating IPs in your Cloud client, then I would recommend undeploying and redeploying the Portal Helm charts, this should refresh the services and assign a new floating IP.
Are all of the portal pods up and running correctly?
1 other possibility is if you have your security groups set up incorrectly, this will prevent your Cloud client from giving ONAP any floating IPs at all. This depends on your Cloud client though.
Regards,
Gareth
Add your comment...
Hi,
ONAP portal not opening after successful installation of casablanca and its in "pending" status.Please let me know any workaround to resolve this issue.
root@kmaster:/opt# kubectl -n onap get services|grep portal
portal-app LoadBalancer 10.230.23.323 <pending> 8989:30215/TCP,8006:30213/TCP,8010:30214/TCP,8443:30225/TCP 19d
portal-cassandra ClusterIP 10.230.55.4 <none> 9160/TCP,7000/TCP,7001/TCP,7199/TCP,9042/TCP 19d
portal-db ClusterIP 10.230.48.23 <none> 3306/TCP 19d
portal-sdk NodePort 10.230.37.3 <none> 8080:30212/TCP 19d
portal-widget ClusterIP 10.230.36.9 <none> 8082/TCP 19d
portal-zookeeper ClusterIP 10.230.15.9 <none> 2181/TCP 19d
sdnc-portal NodePort 10.230.2.19 <none> 8843:30201/TCP
Thanks & Regards