You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest that you add a hint in your wiki to actually use the latest vagrant version for installation. I started with vagrant 2.0.4 and installation failed. The wiki mentioned that at least vagrant 1.5 is required, which I think is misleading.
I tried again with latest (2.1.5) and that did the trick.
Also for Mac OS X it is important to have the readline command available, otherwise the scripts will fail. I installed it with "brew install coreutils". I suggest to add a hint for that too.
Greetings, Richard
p.s.: with vagrant 2.0.4 I got this error
==> sw360-xenial: Running provisioner: puppet...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
Hi SW 360 team,
I suggest that you add a hint in your wiki to actually use the latest vagrant version for installation. I started with vagrant 2.0.4 and installation failed. The wiki mentioned that at least vagrant 1.5 is required, which I think is misleading.
I tried again with latest (2.1.5) and that did the trick.
Also for Mac OS X it is important to have the readline command available, otherwise the scripts will fail. I installed it with "brew install coreutils". I suggest to add a hint for that too.
Greetings, Richard
p.s.: with vagrant 2.0.4 I got this error
==> sw360-xenial: Running provisioner: puppet...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
cp /tmp/vagrant-puppet/vagrant_facts.yaml /etc/puppetlabs/facter/facts.d/vagrant_facts.yaml
The text was updated successfully, but these errors were encountered: