-
Bug
-
Resolution: Done
-
Medium
-
None
-
Amsterdam Release
-
None
-
None
When creating onap in "one click", an error occurs:
Error: release onap-appc failed: Service "dgbuilder" is invalid: spec.ports[0].nodePort: Invalid value: 30228: provided port is already allocated
kubectl get services --all-namespaces says that sdnhost is using it:
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 37m
kube-system heapster ClusterIP 10.43.200.161 <none> 80/TCP 35m
kube-system kube-dns ClusterIP 10.43.0.10 <none> 53/UDP,53/TCP 36m
kube-system kubernetes-dashboard ClusterIP 10.43.163.103 <none> 9090/TCP 36m
kube-system monitoring-grafana ClusterIP 10.43.17.111 <none> 80/TCP 35m
kube-system monitoring-influxdb ClusterIP 10.43.184.177 <none> 8086/TCP 35m
kube-system tiller-deploy ClusterIP 10.43.60.241 <none> 44134/TCP 36m
onap-appc sdnhost NodePort 10.43.246.202 <none> 8282:30230/TCP,1830:30231/TCP 8m
onap-consul consul-server NodePort 10.43.191.194 <none> 8500:30270/TCP,8301:30271/TCP 9m
onap-message-router dmaap NodePort 10.43.96.46 <none> 3904:30227/TCP,3905:30226/TCP 9m
onap-message-router global-kafka ClusterIP None <none> 9092/TCP 9m
onap-message-router zookeeper ClusterIP None <none> 2181/TCP 9m
onap-msb msb-consul NodePort 10.43.3.149 <none> 8500:30500/TCP 9m
onap-msb msb-discovery NodePort 10.43.37.147 <none> 10081:30081/TCP 9m
onap-msb msb-eag NodePort 10.43.15.167 <none> 80:30082/TCP 9m
onap-msb msb-iag NodePort 10.43.218.34 <none> 80:30080/TCP 9m
onap-mso mariadb NodePort 10.43.19.47 <none> 3306:30252/TCP 9m
onap-mso mso NodePort 10.43.231.152 <none> 8080:30223/TCP,3904:30225/TCP,3905:30224/TCP,9990:30222/TCP,8787:30250/TCP 9m
onap-policy brmsgw NodePort 10.43.228.53 <none> 9989:30216/TCP 8m
onap-policy drools NodePort 10.43.237.156 <none> 6969:30217/TCP 8m
onap-policy mariadb ClusterIP None <none> 3306/TCP 8m
onap-policy nexus ClusterIP None <none> 8081/TCP 8m
onap-policy pap NodePort 10.43.7.137 <none> 8443:30219/TCP,9091:30218/TCP 8m
onap-policy pdp NodePort 10.43.238.253 <none> 8081:30220/TCP 8m
onap-portal portalapps NodePort 10.43.226.44 <none> 8006:30213/TCP,8010:30214/TCP,8989:30215/TCP 9m
onap-portal portaldb ClusterIP None <none> 3306/TCP 9m
onap-portal portalwidgets ClusterIP None <none> 8082/TCP 9m
onap-portal vnc-portal NodePort 10.43.75.62 <none> 6080:30211/TCP,5900:30212/TCP 9m
onap-robot robot NodePort 10.43.230.247 <none> 88:30209/TCP 9m
onap-sdnc dbhost ClusterIP None <none> 3306/TCP 9m
onap-sdnc sdnc-dgbuilder NodePort 10.43.91.153 <none> 3000:30203/TCP 9m
onap-sdnc sdnc-portal NodePort 10.43.204.221 <none> 8843:30201/TCP 9m
onap-sdnc sdnctldb01 ClusterIP None <none> 3306/TCP 9m
onap-sdnc sdnctldb02 ClusterIP None <none> 3306/TCP 9m
onap-sdnc sdnhost NodePort 10.43.141.187 <none> 8282:30202/TCP,8201:30228/TCP 9m
onap-vid vid-mariadb ClusterIP None <none> 3306/TCP 9m
onap-vid vid-server NodePort 10.43.182.140 <none> 8080:30200/TCP
9m
I can't find where in configuration sdnhost takes this IP@...