Getting errors on vagrant up

[vatnoise]

Hi,
Trying to run a box and after vagrant up I'm getting the following errors:

....
==> default: stdin: is not a tty
....
==> default: gpg:
==> default: keyring `/tmp/tmprfhgdqk1/secring.gpg' created
==> default: gpg:
==> default: keyring `/tmp/tmprfhgdqk1/pubring.gpg' created
==> default: gpg:
==> default: requesting key 7BB9C367 from hkp server keyserver.ubuntu.com
==> default: gpg:
==> default: /tmp/tmprfhgdqk1/trustdb.gpg: trustdb created
==> default: gpg:
==> default: key 7BB9C367: public key "Launchpad PPA for Ansible, Inc." imported
==> default: gpg:
==> default: Total number processed: 1
==> default: gpg:
==> default:               imported: 1
==> default:   (RSA: 1)
....
==> default: dpkg-preconfigure: unable to re-open stdin: No such file or directory
....
==> default: cp:
==> default: cannot stat ‘/vagrant/ansible/inventories/dev’
==> default: : No such file or directory
==> default: cat:
==> default: /vagrant/ansible/files/authorized_keys
==> default: : No such file or directory
==> default: ERROR! the playbook: /vagrant/ansible/playbook.yml could not be found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I usually used already pre-made vagrant boxes before and creating my own for the first time.

[debo]

@vatnoise that's interesting, could you please share the package you downloaded? By the look of it the errors indicate you are missing most of the essential files. I'd like to make a comparison between I what I have and what you got.

[vatnoise]

Sure!
I've unfortunately closed the window with the settings that I chose but here are the 2 packages that I got from it:

phansible_default.zip
phansible_default (1).zip

[vatnoise]

Just made another one in Firefox, here's the file and screenshots:

phansible__box_php5.4_xdebug.zip

[debo]

@vatnoise I just tried the first one of the zips you linked and it worked for me. I'm running vagrant 1.8.5 and the VirtualBox 5.0.20 at the moment, I'm going to have a go with the latest version of VirtualBox too and report back.

[debo]

@vatnoise it works also with VirtualBox 5.1.2 over here and the same package. Just out of curiosity what OS are your running? I'm on OSX here.

[vatnoise]

@debo OS X 10.11.5, VirtualBox 5.0.22

I'll try updating VirtualBox later today and will see if that changes anything. :(

[debo]

@vatnoise please keep me posted as of now it looks more like a glitch of sort mostly related with ansible itself not detecting path properly for some weird reasons. The zips you share with me contains all the required files including the one your error log sais are not found.

[vatnoise]

Hm, updated VirtualBox to 5.0.26, still the same. I guess there's probably something wrong with my system?

[debo]

@vatnoise the latest virtualbox version is 5.1.2. Yes the problem appears to be related to something else in your setup. Basically what is happening in your case is that the shared folder between your host and guest doesn't get shared or, if it does, it suddenlly disappear so that ansible can't find the files it needs.

In fairness there is one thing that seems strange about your setup, although it doesn't seem to affect my test. So basically if I look at the vagrant file you generated you are sharing the following:

config.vm.synced_folder "/Users/vitalibokov/GitHub/", "/vagrant", type: "nfs"

And the error message is reporting the following:

cannot stat ‘/vagrant/ansible/inventories/dev’

now the thing is that the ansible folder is not in your home right? The ansible folder is in the path from where you launch or should launch vagrant up and you can see that in these lines:

config.vm.provision "ansible" do |ansible|
    ansible.playbook = "ansible/playbook.yml"
    ansible.inventory_path = "ansible/inventories/dev"
    ansible.limit = 'all'
end

So my question is, how are you executing all this? Are the file in the right and expected location or did you accidentally moved things around?

Could you also post a gist of the entire log? I'd like to see at what step you error is actually getting thrown also because I can't see that output in my terminal (I'm referring about the gpg import)

[debo]

@vatnoise did you have any luck with this? Any progress?