Tina, Harry,
Hi, sorry to hear that. Could you post your environment (Ubuntu 16.04 ?)
We can compare network setups then as I have not seen an IPV6 issue yet.
Are you seeing all 6 pods of the k8s/rancher stack
Post your results from a
Kubectl get pods –all-namespaces –a
You should see all 1/1 or 3/3
There are sometimes issues with a clustered rancher setup where the dns pod
is 0/1 above.
Thank you
/michael
From: Tina Tsou [mailto:tina.t...@arm.com]
Sent: Thursday, September 7, 2017 03:31
To: huangxiangyu <huangxiang...@huawei.com>; Michael O'Brien
<frank.obr...@amdocs.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Auto] Error when create onap pods using
kubernetes
Dear Frank,
Would you like to help here?
Thank you,
Tina
On Sep 6, 2017, at 7:03 PM, huangxiangyu
<huangxiang...@huawei.com<mailto:huangxiang...@huawei.com>> wrote:
Hi Tina
Here is the error log of the main issue I met when perform ONAP deploy
according to https://wiki.onap.org/display/DW/ONAP+on+Kubernetes.
Creating deployments and services **********
E0907 01:24:17.232548 42374 portforward.go:209] Unable to create listener:
Error listen tcp6 [::1]:51
444: bind: cannot assign requested address
NAME: mso
LAST DEPLOYED: Thu Sep 7 01:24:38 2017
NAMESPACE: onap
STATUS: DEPLOYED
RESOURCES:
==> v1/Service
NAME CLUSTER-IP EXTERNAL-IP PORT(S)
AGE
mariadb 10.43.13.178 <nodes> 3306:30252/TCP
0s
mso 10.43.53.224 <nodes>
8080:30223/TCP,3904:30225/TCP,3905:30224/TCP,9990:30222/TCP,8787:30
250/TCP 0s
==> extensions/v1beta1/Deployment
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
mariadb 1 1 1 0 0s
mso 1 1 1 0 0s
I try to enable ipv6 on host server but still can’t fix the error. Maybe you
can find some help with this?
Thanks
Harry
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
