We are also stuck in same error. Is there anyway to standup devKit in dockerized mode ( primarily using docker compose ) as opposed to struggling with vagrant onap ?
BR, Viswa <http://www.verizon.com> Viswanath Kumar Skand Priya Architect Verizon Network Ops & Eng On Thu, Nov 30, 2017 at 4:40 PM, <[email protected]> wrote: > Done it, but there is still the same error > > > > *De :* Moshe Hoadley [mailto:[email protected]] > *Envoyé :* jeudi 30 novembre 2017 12:02 > > *À :* JEZEQUEL Mickael IMT/OLN; [email protected] > *Objet :* RE: [vvp] devkit: errors during vagrant up execution > > > > Under the devkit folder, try to run: > > ./bin/vvp-install-box > > (you may need to chmod +x first) > > > > Thanks > > Moshe Hoadley > > *(* 972-9-77-62712 > > [image: cid:[email protected]] > > > > *From:* [email protected] [mailto:[email protected] > <[email protected]>] > *Sent:* Thursday, November 30, 2017 12:44 PM > *To:* Moshe Hoadley <[email protected]>; > [email protected] > *Subject:* RE: [vvp] devkit: errors during vagrant up execution > > > > Thank you very much for your answer. > > > > I have already tried it. The ovf file is then correctly parsed, but it > failed just after, complaining that the vmdk file is missing: > > > > VBoxManage: error: Appliance import failed > > VBoxManage: error: Error opening '/home/mj/.vagrant.d/boxes/ > vvp-empty/0/virtualbox/vvp_empty_vagrant_image.vmdk' for reading > (VERR_FILE_NOT_FOUND) > > > > > > > > *De :* Moshe Hoadley [mailto:[email protected] > <[email protected]>] > *Envoyé :* jeudi 30 novembre 2017 11:23 > *À :* JEZEQUEL Mickael IMT/OLN; [email protected] > *Objet :* RE: [vvp] devkit: errors during vagrant up execution > > > > Hi > > For Item #3, remove the copyright lines from the beginning of the > ‘box.ovf’ file it is not legal xml syntax. > > I’m also stuck on items 1 and 2 > > > > Thanks > > Moshe Hoadley > > *(* 972-9-77-62712 > > [image: cid:[email protected]] > > > > *From:* [email protected] [mailto:onap-discuss-bounces@ > lists.onap.org <[email protected]>] *On Behalf Of * > [email protected] > *Sent:* Thursday, November 30, 2017 11:40 AM > *To:* [email protected] > *Subject:* [onap-discuss] [vvp] devkit: errors during vagrant up execution > > > > Hi everyone , > > > > I'm trying to run the vvp project , but I’m facing several pb during the > setup: > > > > 1) Vagrant is stucked during “vagrant up” during ops-01 network > configuration. > > The last log lines are: > > ==> ops-01: Machine booted and ready! > > ==> ops-01: Configuring and enabling network interfaces... > > > > I have found a temporary workaround by commenting the following line in > Vagrantfile: > > :nic_type => "virtio", > > > > Does anyone know the reason of this behavior ? > > > > > > 2) With the previous modification, the vagrant setup is fine for > ops-01, but ceph-01 setup get stucked during the ansible configuration : > > > > TASK [ceph.ceph-rgw : is ceph running already?] > ******************************** > > [DEPRECATION WARNING]: always_run is deprecated. Use check_mode = no > instead.. > > > > This feature will be removed in version 2.4. Deprecation warnings can be > > disabled by setting deprecation_warnings=False in ansible.cfg. > > > > > > when I tried to execute manually the blocking command on the ceph-01 vm, > I got the following error: > > ceph --connect-timeout 3 --cluster ceph fsid > > 2017-11-30 08:50:08.398284 7ff725444700 -1 auth: unable to find a keyring > on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph. > keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or > directory > > > > > > 3) core-os1 setup fails right at the beginning: > > > > ==> coreos-01: Importing base box 'vvp-empty'... > > 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/mj/.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/mj/.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 > > > > > > My environment is Ubuntu 17.04 > > with vagrant 2.0.1, virtualbox 5.2.2 and ansible 2.2.1.0 > > > > Am I missing anything ? . Can anyone help in this issue?. > > > > [image: logo Orange] > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.orange.com_&d=DwMFAw&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=U8hY_Zsdy5kPCl7TvfoGnXL53_13rxVKwpYLqio982o&s=AKtN8Z5D1GOLm6vd2RE5DpfHhfVD-1U-Kd66HcueN4g&e=> > > > > *Mickael Jezequel * > > > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete > this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > > 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAw&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=U8hY_Zsdy5kPCl7TvfoGnXL53_13rxVKwpYLqio982o&s=qG_nk0mmbPccc5AN_l4YHnjz80JTXZ_Rg5mNKjE_dew&e=> > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete > this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > > 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAw&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=U8hY_Zsdy5kPCl7TvfoGnXL53_13rxVKwpYLqio982o&s=qG_nk0mmbPccc5AN_l4YHnjz80JTXZ_Rg5mNKjE_dew&e=> > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > > _______________________________________________ > onap-discuss mailing list > [email protected] > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. > onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c= > udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE- > 2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=U8hY_ > Zsdy5kPCl7TvfoGnXL53_13rxVKwpYLqio982o&s=ptCqMUjIPB78tOtqxNwwZOOMDV9bmk > CyNJ8xmlagkRM&e= > >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
