-
Bug
-
Resolution: Done
-
Medium
-
Amsterdam Release, Beijing Release
-
None
-
OOM Sprint 7
Hi,
When I was trying to access CLI in vnc-portal by typing http://10.43.70.106:8080 in firefox, unfortunately there was no response and connection had timed out.
I checked the kubernetes service for CLI, it seemed only exposed 80 port. But in CLI project under https://git.onap.org/cli/tree/deployment/docker/src/main/docker/docker-compose.yaml, it told me that there should be 2 exposed port 8080->80, 9090->8080. It means the kubernetes service for CLI should expose 8080 and 9090 ports.
onap@onap-ProLiant-DL360-Gen9:~/setup/oom-amsterdam/kubernetes/oneclick$ kubectl get services --all-namespaces -o wide|grep cli
onap-cli cli NodePort 10.43.70.106 <none> 80:30260/TCP 21h app=cli
services:
occ:
image: onap/cli
environment:
OPEN_CLI_MODE: 'daemon'
ports:
- 8080:80
- 9090:8080
onap@onap-ProLiant-DL360-Gen9:~/setup/oom-amsterdam/kubernetes/cli/templates$ kubectl exec -it cli-1971128182-p1mwg bash -n onap-cli
root@cli-1971128182-p1mwg:/opt/onap/cli# netstat -nltp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN -
tcp6 0 0 :::8080 :::* LISTEN 16/gotty