onap-vfc-ems-driver pod not starting due to a bad configuration

should be fixed by https://gerrit.onap.org/r/c/oom/+/101210

In CI daily master/CI gating, this pod does not start properly because of a misconfiguration of MSB

see https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/jobs/427699462/artifacts/download

Name: onap-vfc-ems-driver-68d5d975fb-tmmwq
Namespace: onap
Priority: 0
Node: compute02-onap-master/10.253.0.8
Start Time: Thu, 06 Feb 2020 06:38:38 +0000
Labels: app=vfc-ems-driver
pod-template-hash=68d5d975fb
release=onap
Annotations: sidecar.istio.io/inject: true
Status: Running
IP: 10.233.67.200
Controlled By: ReplicaSet/onap-vfc-ems-driver-68d5d975fb
Containers:
vfc-ems-driver:
Container ID: docker://28af1095cfd2ec5708c8d6e5f1aade3813587d5d4278be4e7789972d80b809e2
Image: nexus3.onap.org:10001/onap/vfc/emsdriver:1.3.0
Image ID: docker-pullable://nexus3.onap.org:10001/onap/vfc/emsdriver@sha256:2f6676ec622480e13994240778e87b8e35664116fd04159a0a53d330d36bcdd2
Port: 8206/TCP
Host Port: 0/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Thu, 06 Feb 2020 07:01:46 +0000
Finished: Thu, 06 Feb 2020 07:04:44 +0000
Ready: False
Restart Count: 7
Liveness: tcp-socket :8206 delay=120s timeout=1s period=10s #success=1 #failure=3
Readiness: tcp-socket :8206 delay=10s timeout=1s period=10s #success=1 #failure=3
Environment:
MSB_ADDR: msb-iag:80
VES_ADDR: dcae-ves-collector:8080
VES_AUTHINFO: :
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-l962t (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-l962t:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-l962t
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 28m default-scheduler Successfully assigned onap/onap-vfc-ems-driver-68d5d975fb-tmmwq to compute02-onap-master
Normal Created 25m kubelet, compute02-onap-master Created container vfc-ems-driver
Normal Started 25m kubelet, compute02-onap-master Started container vfc-ems-driver
Normal Killing 23m kubelet, compute02-onap-master Container vfc-ems-driver failed liveness probe, will be restarted
Warning Unhealthy 23m (x3 over 23m) kubelet, compute02-onap-master Liveness probe failed: dial tcp 10.233.67.200:8206: connect: connection refused
Normal Pulled 22m (x2 over 25m) kubelet, compute02-onap-master Successfully pulled image "nexus3.onap.org:10001/onap/vfc/emsdriver:1.3.0"
Normal Pulling 7m55s (x7 over 28m) kubelet, compute02-onap-master Pulling image "nexus3.onap.org:10001/onap/vfc/emsdriver:1.3.0"
Warning Unhealthy 2m55s (x123 over 25m) kubelet, compute02-onap-master Readiness probe failed: dial tcp 10.233.67.200:8206: connect: connection refused
SERVICE_IP=10.233.67.200
MSB_ADDR=msb-iag:80
Wait for MSB initialization
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused
curl: (7) Failed connect to msb-iag:80; Connection refused

MSB is no more exposed on the port 80 => move to 443

Please update the helm chart accordingly

the problem is reproducible and trigger errors on some robot healthcheck tests