Hi Team and Srini,
- For the vFW cnf usecase in Frankfurt scope, kud cluster is brought up on a VM
in our openstack private cloud by following link:
https://wiki.onap.org/display/DW/Kubernetes+Baremetal+deployment+setup+instructions.
- The vFW instantiation is successful and the outpost is as mentioned in the
file Instantiation_output.txt.
- But the pods not came up as a part of instantiation. When kubectl CS and
nodes are checked the error is as mentioned below:
root@kud:/home/ubuntu/k8s/kud/hosting_providers/vagrant# kubectl get nodes
NAME STATUS ROLES AGE VERSION
localhost NotReady master 45m v1.18.9
root@kud:/home/ubuntu/k8s/kud/hosting_providers/vagrant#
root@kud:/home/ubuntu/k8s/kud/hosting_providers/vagrant#
root@kud:/home/ubuntu/k8s/kud/hosting_providers/vagrant# kubectl get cs
NAME STATUS MESSAGE
ERROR
controller-manager Unhealthy Get http://127.0.0.1:10252/healthz: dial tcp
127.0.0.1:10252: connect: connection refused
scheduler Unhealthy Get http://127.0.0.1:10251/healthz: dial tcp
127.0.0.1:10251: connect: connection refused
etcd-0 Healthy {"health":"true"}
We are suspecting that these errors are causing for the pods to comeup in
kud-cluster.
Any inputs or suggesstions for this issue to resolve are appreciated.
Thanks and Regards,
Naveen
L&T Technology Services Ltd
www.LTTS.com
L&T Technology Services Limited (LTTS) is committed to safeguard your data
privacy. For more information to view our commitment towards data privacy under
GDPR, please visit the privacy policy on our website www.Ltts.com. This Email
may contain confidential or privileged information for the intended recipient
(s). If you are not the intended recipient, please do not use or disseminate
the information, notify the sender and delete it from your system.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22662): https://lists.onap.org/g/onap-discuss/message/22662
Mute This Topic: https://lists.onap.org/mt/79122552/21656
Mute #k8splugin:https://lists.onap.org/g/onap-discuss/mutehashtag/k8splugin
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
root@kud:/home/ubuntu/k8s/kud/hosting_providers/vagrant# kubectl get
pods,svc,networks,cm,network-attachment-definition,deployments
NAME TYPE
CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/k8sregionfour-onap-nf-20201221t073916731z-vpkg-vfmt-001-mgmt NodePort
10.244.43.175 <none> 2831:30831/TCP 65m
service/k8sregionfour-onap-nf-20201221t073916731z-vsn-vfmt-001-ui NodePort
10.244.15.175 <none> 667:30667/TCP 65m
service/kubernetes
ClusterIP 10.244.0.1 <none> 443/TCP 94m
NAME
AGE
network.k8s.plugin.opnfv.org/k8sregionfour-onap-nf-20201221t073916731z-management-network
65m
network.k8s.plugin.opnfv.org/k8sregionfour-onap-nf-20201221t073916731z-protected-network
65m
network.k8s.plugin.opnfv.org/k8sregionfour-onap-nf-20201221t073916731z-unprotected-network
65m
network.k8s.plugin.opnfv.org/ovn-port-net
77m
network.k8s.plugin.opnfv.org/ovn-priv-net
77m
NAME
DATA AGE
configmap/k8sregionfour-onap-nf-20201221t073916731z-vfw-vfmt-001-configmap 6
65m
configmap/k8sregionfour-onap-nf-20201221t073916731z-vpkg-vfmt-001-configmap 6
65m
configmap/k8sregionfour-onap-nf-20201221t073916731z-vsn-vfmt-001-configmap 2
65m
NAME
AGE
networkattachmentdefinition.k8s.cni.cncf.io/bridge-conf
77m
networkattachmentdefinition.k8s.cni.cncf.io/ipvlan-conf
77m
networkattachmentdefinition.k8s.cni.cncf.io/k8sregionfour-onap-nf-20201221t073916731z-ovn-nat
65m
networkattachmentdefinition.k8s.cni.cncf.io/macvlan-conf
77m
networkattachmentdefinition.k8s.cni.cncf.io/ovn-networkobj
90m
networkattachmentdefinition.k8s.cni.cncf.io/ptp-conf
77m
NAME READY
UP-TO-DATE AVAILABLE AGE
deployment.apps/k8sregionfour-onap-nf-20201221t073916731z-vfw-vfmt-001 0/1
0 0 65m
deployment.apps/k8sregionfour-onap-nf-20201221t073916731z-vpkg-vfmt-001 0/1
0 0 65m
deployment.apps/k8sregionfour-onap-nf-20201221t073916731z-vsn-vfmt-001 0/1
0 0 65m
deployment.apps/multus-deployment 0/1
0 0 77m
deployment.apps/ovn4nfv-deployment 0/1
0 0 77m
deployment.apps/virtlet-deployment 0/1
0 0 78m
