Hi Unfortunately, I couldn't solve it. My conclusion is that it is a centos7 issue. A work-around: - Kill the vagrant process once it's stuck and run it again. - Vagrant will see that the VM is already up and will skip to the next VM. - Vagrant will again be stuck on the second VM, repeat the kill and re run procedure. - Vagrant will see that 2 VMs are already up and will skip to the third VM. - The 3rd VM is of COREOS and it doesn't get stuck.
At this point ansible starts running and fails on the missing roles folder. Thanks Moshe Hoadley M 972-9-77-62712 -----Original Message----- From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Binshtok, Edan Sent: Tuesday, November 21, 2017 8:26 PM To: Karthik <sdkarth...@gmail.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] VVP-devkit : Problem Hi Karthik, Happy to meet you. I’ll be glad if you can share in a couple of words who you are and from what company, just so we all get to know each other ☺ I’m Edan Binshtok from AT&T and I was one of the original developer which seeded the code. Looks like a bad network issue. 1. Can you check there isn’t a problematic network adapter in virtualbox ? 2. Did you add the “# 10.252.0.12 coreos-01.development.vvp.example.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__coreos-2D01.development.vvp.example.com&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=D1Kpn0JKEKYKQ4Uw-5KS9O0Z8LdD2ncTKA3PFYjaFUw&s=L9rX6Yxf2t4-5P_6m3kkUL07s1PPdilymlMduXpMu6E&e=>” to your known hosts? Moshe, Sandeep, Paul, something else you can think of? From: Karthik <sdkarth...@gmail.com> Date: Tuesday, 21 November 2017 at 17:28 To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, "Binshtok, Edan" <eb5...@intl.att.com> Subject: VVP-devkit : Problem Hi Team , I am using VVP/devkit project . I have all setups in my Linux environment (Ubuntu 16). I followed the READ.ME<https://urldefense.proofpoint.com/v2/url?u=http-3A__READ.ME&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=D1Kpn0JKEKYKQ4Uw-5KS9O0Z8LdD2ncTKA3PFYjaFUw&s=lN1oK148aBEhzeXklpDtPQiGggRitZ9NKQcinRUbJ94&e=> file as mentioned below; # update your hosts file with the line # 10.252.0.12 coreos-01.development.vvp.example.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__coreos-2D01.development.vvp.example.com&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=D1Kpn0JKEKYKQ4Uw-5KS9O0Z8LdD2ncTKA3PFYjaFUw&s=L9rX6Yxf2t4-5P_6m3kkUL07s1PPdilymlMduXpMu6E&e=> . setenv # select the envirionment yout want from the list vagrant up watch -n5 "kubectl get po -n kube-system" # once all pods are running status `bin/vvp-deploy` When I launched vagrant up , It keeps hanging at the below line "ops-01: Configuring and enabling network interfaces".Please refer pic1. kubectl is fails with the below error : Unable to connect to the server: dial tcp: lookup localhost on 8.8.8.8:53<https://urldefense.proofpoint.com/v2/url?u=http-3A__8.8.8.8-3A53&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=D1Kpn0JKEKYKQ4Uw-5KS9O0Z8LdD2ncTKA3PFYjaFUw&s=jM_p20wLvmpqvlSFgjcA3xKruCrGdJp1qEIiJVUagks&e=>: no such host Am I missing anything ? . Can anyone help in this issue?. _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss 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> _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
