+Kural From: [email protected] <[email protected]> On Behalf Of Lukasz Rajewski via lists.onap.org Sent: Monday, December 21, 2020 11:49 AM To: Sood, Ritu <[email protected]>; [email protected]; [email protected]; Addepalli, Srinivasa R <[email protected]>; Multanen, Eric W <[email protected]>; '[email protected]' <[email protected]> Cc: Velugubantla Praveen <[email protected]> Subject: Re: [onap-discuss] #k8splugin vFW instantiation issue in frankfurt
We, I am not sure of this is a real problem. I need to re-run vFW on my cluster. Component Statuses are deprecated, I could install quickly grafana on my cluster so it looks that k8s cluster works in general. Naveen has different situation as for him node is not ready while for me it is fine. I will let you after I run vFW. Regards, [Logo Orange] Łukasz Rajewski, R&D Expert Orange Labs Poland, Advanced Network Solutions Agency Mob.: +48 519 310 854 Orange Polska, Obrzeżna 7, 02-691 Warsaw www.orange.pl<http://www.orange.pl/> From: Sood, Ritu <[email protected]<mailto:[email protected]>> Sent: Monday, December 21, 2020 7:46 PM To: Rajewski Łukasz - Hurt <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Addepalli, Srinivasa R <[email protected]<mailto:[email protected]>>; Multanen, Eric W <[email protected]<mailto:[email protected]>>; '[email protected]' <[email protected]<mailto:[email protected]>> Cc: Velugubantla Praveen <[email protected]<mailto:[email protected]>> Subject: RE: #k8splugin vFW instantiation issue in frankfurt Hi Lukasz Is this problem only for the vFW use case or KUD in general? Thanks Ritu From: Rajewski Łukasz - Hurt <[email protected]<mailto:[email protected]>> Sent: Monday, December 21, 2020 10:20 AM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Addepalli, Srinivasa R <[email protected]<mailto:[email protected]>>; Sood, Ritu <[email protected]<mailto:[email protected]>>; Multanen, Eric W <[email protected]<mailto:[email protected]>>; '[email protected]' <[email protected]<mailto:[email protected]>> Cc: Velugubantla Praveen <[email protected]<mailto:[email protected]>> Subject: RE: #k8splugin vFW instantiation issue in frankfurt OK, it is not enough. I can reproduce the same mostly but for me node has status Ready, but both scheduler and controller-manager cs are Unhealthy. Regards, [Logo Orange] Łukasz Rajewski, R&D Expert Orange Labs Poland, Advanced Network Solutions Agency Mob.: +48 519 310 854 Orange Polska, Obrzeżna 7, 02-691 Warsaw www.orange.pl<http://www.orange.pl/> From: Rajewski Łukasz - Hurt Sent: Monday, December 21, 2020 6:55 PM To: [email protected]<mailto:[email protected]>; '[email protected]' <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; Sood, Ritu ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>>; Multanen, Eric W ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>>; '[email protected]' <[email protected]<mailto:[email protected]>> Cc: Velugubantla Praveen <[email protected]<mailto:[email protected]>> Subject: RE: #k8splugin vFW instantiation issue in frankfurt Including others that can provide valuable input. I am sure it is enough to add extra step before ./aio.sh export KUD_ADDONS="virtlet ovn4nfv" Regards, [Logo Orange] Łukasz Rajewski, R&D Expert Orange Labs Poland, Advanced Network Solutions Agency Mob.: +48 519 310 854 Orange Polska, Obrzeżna 7, 02-691 Warsaw www.orange.pl<http://www.orange.pl/> From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Naveen S. Sankad Sent: Monday, December 21, 2020 10:57 AM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: Velugubantla Praveen <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] #k8splugin vFW instantiation issue in frankfurt 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<http://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<http://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 (#22667): https://lists.onap.org/g/onap-discuss/message/22667 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]] -=-=-=-=-=-=-=-=-=-=-=-
