I figure out the root cause. The vm host has default proxy setup as the VM instance is created. Looks Helm port forward is not working due to default http/s-proxy setup. By unset the http proxy, the helm install is working and onap installation is resume.
[suggestion to update the wiki about the tips: unset the http proxy of install shell in a private cloud before installation] Issue can be closed. Thanks. Br Jeffrey From: Li, Jeffrey (NSB - CN/Chengdu) Sent: Tuesday, December 12, 2017 4:01 PM To: '[email protected]' <[email protected]> Subject: Installation ONAP on K8S, stuck at helm chart installation for config pod creation Hi, I am installation ONAP on Kubernete on EE Cloud (openstack based), following the instructions on wiki: https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-ONAPMinimumR1InstallationHelmApps Everything is ok until creating the config pod. root@onap3:~/oom/kubernetes/config# ./createConfig.sh -n onap **** Creating configuration for ONAP instance: onap namespace "onap" created E1212 06:24:00.690049 31344 portforward.go:175] lost connection to pod Error: transport is closing **** Done **** I tried many times from scratch and problem remains the same. root@onap3:~/oom/kubernetes/config# helm version Client: &version.Version{SemVer:"v2.3.0", GitCommit:"d83c245fc324117885ed83afc90ac74afed271b4", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.3.0", GitCommit:"d83c245fc324117885ed83afc90ac74afed271b4", GitTreeState:"clean"} Any ideas on this helm error, I googling and no found the answer. Br Jeffre
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
