I've got a RHEL 7.2 machine running chefdk 0.7.0 and vagrant 1.8.1 with the 
vmware plugin installed.

When I do a kitchen create I get the following error:


[wyatt@oc4642434687 ei-bootcamp]$ kitchen create
-----> Starting Kitchen (v1.4.2)
-----> Creating <default-RHEL>...
       Bringing machine 'default' up with 'vmware_workstation' provider...
       ==> default: Cloning VMware VM: 'IBM.EI.RHEL.6'. This can take some 
time...
       ==> default: Checking if box 'IBM.EI.RHEL.6' is up to date...
       ==> default: Skipping vmnet device verification, verify_vmnet is set 
to false.
       ==> default: Preparing network adapters...
       ==> default: Starting the VMware VM...
       ==> default: Waiting for machine to boot. This may take a few 
minutes...    default: SSH address: 192.168.211.140:22
           default: SSH username: vagrant
           default: SSH auth method: private key
           default: Warning: Connection refused. Retrying...
           default: Warning: Connection refused. Retrying...
           default: 
           default: Vagrant insecure key detected. Vagrant will 
automatically replace
           default: this with a newly generated keypair for better security.
           default: 
           default: Inserting generated public key within guest...
           default: Removing insecure key from the guest if it's present...
           default: Key inserted! Disconnecting and reconnecting using new 
SSH key...
       ==> default: Machine booted and ready!
       ==> default: Forwarding ports...
           default: -- 80 => 8080
           default: -- 22 => 2222
       ruby: error while loading shared libraries: libruby.so.2.2: cannot 
open shared object file: No such file or directory
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #create action: [Expected process to 
exit with [0], but received '1'
---- Begin output of vagrant up --no-provision --provider 
vmware_workstation ----
STDOUT: Bringing machine 'default' up with 'vmware_workstation' provider...
==> default: Cloning VMware VM: 'IBM.EI.RHEL.6'. This can take some time...
==> default: Checking if box 'IBM.EI.RHEL.6' is up to date...
==> default: Skipping vmnet device verification, verify_vmnet is set to 
false.
==> default: Preparing network adapters...
==> default: Starting the VMware VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 192.168.211.140:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection refused. Retrying...
    default: Warning: Connection refused. Retrying...
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically 
replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH 
key...
==> default: Machine booted and ready!
==> default: Forwarding ports...
    default: -- 80 => 8080
    default: -- 22 => 2222
STDERR: ruby: error while loading shared libraries: libruby.so.2.2: cannot 
open shared object file: No such file or directory
---- End output of vagrant up --no-provision --provider vmware_workstation 
----
Ran vagrant up --no-provision --provider vmware_workstation returned 1]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration


I had a similar issue with vagrant 1.7.4 (except the error was with 
libruby.so.2.0).  If I add an "export 
LD_LIBRARY_PATH=opt/vagrant/embedded/lib" to my profile then it works.

Any ideas what could be wrong?  When I was on RHEL 6.7 I didn't have this 
same issue, even with the same levels of chef and vagrant.

Thanks.

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/12e5d25a-91c4-4425-a690-8991b1bf859c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to