Didn’t encounter this. Can you check if the folder exists: home/karthik/.vagrant.d/boxes/vvp-empty/0/virtualbox/box.ovf
Also, for the workaround, you need to get to a position where the 2 first vms are up and running (you can see it in the vritualbox gui. To open the gui just type ‘virtualbox’). The third vm should not exist at all so, in order to try again, first go and delete the 3rd vm. Let me know how it goes. Thanks Moshe Hoadley • 972-9-77-62712 [cid:[email protected]] From: Karthik [mailto:[email protected]] Sent: Friday, November 24, 2017 10:05 AM To: Moshe Hoadley <[email protected]> Cc: Binshtok, Edan <[email protected]>; [email protected] Subject: Re: [onap-discuss] [E] Re: VVP-devkit : Problem Hi Moshe , I pulled the latest code and followed your work around . I got the below error when it tries to launch 3rd VM. There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below. Command: ["import", "-n", "/home/karthik/.vagrant.d/boxes/vvp-empty/0/virtualbox/box.ovf"] Stderr: 0%... Progress state: VBOX_E_FILE_ERROR VBoxManage: error: Appliance read failed VBoxManage: error: Start tag expected, '<' not found. VBoxManage: error: Location: '/home/karthik/.vagrant.d/boxes/vvp-empty/0/virtualbox/box.ovf', line 1 (0), column 1 VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 307 of file VBoxManageAppliance.cpp Please refer the attached image. Hi Team, Could you please suggest me some other way to debug it ?. I will try it out. Thanks, Karthik On Thu, Nov 23, 2017 at 7:00 PM, Moshe Hoadley <[email protected]<mailto:[email protected]>> wrote: Hi Ansible is failing with ssh to localhost. After investigation, I found that ansible uses the user 'vagrant' to ssh to localhost. However, the user on localhost is my own username ('devel'). Could you please check it out? Am I missing something? Should I have created a user called 'vagrant' in my dev mchine? Thanks Moshe Hoadley M 972-9-77-62712 -----Original Message----- From: Binshtok, Edan [mailto:[email protected]<mailto:[email protected]>] Sent: Thursday, November 23, 2017 2:08 PM To: Moshe Hoadley <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; Karthik <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] [E] Re: VVP-devkit : Problem Hi moshe can you send us the git status / git diff and terminal log so we can see what going on and how you got to this problem? On 23/11/2017, 14:06, "Moshe Hoadley" <[email protected]<mailto:[email protected]>> wrote: Hi There is a missing file under devkit: ./zones/k8/kubeconfig Thanks Moshe Hoadley M 972-9-77-62712 -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Binshtok, Edan Sent: Wednesday, November 22, 2017 9:07 AM To: Kumar Skand Priya, Viswanath V <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; Karthik <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] [E] Re: VVP-devkit : Problem Great, Happy to have you guys onboard. Welcome to the Team. Edan From: "Kumar Skand Priya, Viswanath V" <[email protected]<mailto:[email protected]>> Date: Tuesday, 21 November 2017 at 20:47 To: "Binshtok, Edan" <[email protected]<mailto:[email protected]>> Cc: Karthik <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [E] Re: [onap-discuss] VVP-devkit : Problem Hi Edan, Good Day! Karthik works in my team and we are from Verizon. We are currently exploring VVP in isolated lab, which isn't connected to our corporate network. Hence he would be using gmail to clarify his queries. Thanks for your help & glad to meet you. BR, Viswa [https://urldefense.proofpoint.com/v2/url?u=http-3A__ss7.vzw.com_is_image_VerizonWireless_vz-2Dsig-2Dverizon-3F-24defaultscale-24&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=OK9V3EMBZuwAeYu6nWmfqjH8uWayXVj0s2iIF7FtLvg&s=teyuQyi7wYGr-CjlCldoJuTHVVIeTnFXqX4TIRNY8TU&e= ]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.verizon.com&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=SQcqwHX8liYlcb39b60Yh02dGPqCO_WL4i8_ypr6pAw&s=QdX9y6Yfe7ExMZ5BWhbnAib06wMBYXYCBO9xD0JmtMs&e=> Viswanath Kumar Skand Priya Architect Verizon Network Ops & Eng On Tue, Nov 21, 2017 at 11:56 PM, Binshtok, Edan <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote: 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<http://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=SQcqwHX8liYlcb39b60Yh02dGPqCO_WL4i8_ypr6pAw&s=O69QdtMNFrCjseRqC2qo7SBvQCkdC8IXGuecK9iWRZ8&e=><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 <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> Date: Tuesday, 21 November 2017 at 17:28 To: "[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>, "Binshtok, Edan" <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> 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<http://READ.ME><https://urldefense.proofpoint.com/v2/url?u=http-3A__READ.ME&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=SQcqwHX8liYlcb39b60Yh02dGPqCO_WL4i8_ypr6pAw&s=Lh_L1M3ot9-Ctt5KjyVSBN3RWPSJtOPSedYPGV-Gw78&e=><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<http://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=SQcqwHX8liYlcb39b60Yh02dGPqCO_WL4i8_ypr6pAw&s=O69QdtMNFrCjseRqC2qo7SBvQCkdC8IXGuecK9iWRZ8&e=><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<http://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=SQcqwHX8liYlcb39b60Yh02dGPqCO_WL4i8_ypr6pAw&s=PFowoIOHcJFd2TU3fYK1HFZDKs9ABeLX06ZRzyH4o44&e=><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 [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=b3kuQL-kk0YFKp3nSEQvT28jtUqhVi_elPutPsQ29go&s=hEkzkA9aVtmJZqD15PDaq2IyUYxRpSiCEX8MxHuhWpY&e= _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=OK9V3EMBZuwAeYu6nWmfqjH8uWayXVj0s2iIF7FtLvg&s=AuycTYIyGEfFZTiW0M5ePn2gpyinJlYVpyEACoyvlDc&e= This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=OK9V3EMBZuwAeYu6nWmfqjH8uWayXVj0s2iIF7FtLvg&s=R5zqSCQjm43cvyddlcU-6eEgvv-R_B8F1yHh7ry5Pss&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec&m=OK9V3EMBZuwAeYu6nWmfqjH8uWayXVj0s2iIF7FtLvg&s=R5zqSCQjm43cvyddlcU-6eEgvv-R_B8F1yHh7ry5Pss&e= > 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> 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 [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
