Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SMB shared folders doesn't appear to work #68

Open
StevenArmstrong opened this issue May 21, 2014 · 4 comments
Open

SMB shared folders doesn't appear to work #68

StevenArmstrong opened this issue May 21, 2014 · 4 comments

Comments

@StevenArmstrong
Copy link

Hi

I am trying to use vagrant 1.6.2 and test the shared folder functionality with vagrant-vsphere and it appears to always try and default to rsync. Am I doing something horribly wrong or is this just not supported yet with the vsphere provider?
I am using a windows host and guest,
My vagrantfile is as follows:

Vagrant.configure("2") do |config|

config.vm.define :TestBox do |config|
config.windows.halt_timeout = 15
config.winrm.username = "Administrator"
config.winrm.password = "******"
config.vm.box = "TestBox"
config.vm.communicator = "winrm"
config.berkshelf.enabled = true

config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct:true

config.vm.box_url = "./TestBox.box"
config.vm.synced_folder ".", "/vagrant", type: "smb"

config.vm.provision "chef_solo" do |chef|
chef.log_level = :info
chef.custom_config_path = "Vagrantfile.chef"
chef.add_recipe "windows::TestRunBook"

end

config.vm.provider :vsphere do |vsphere|
vsphere.host = '10.20.1.67'
vsphere.compute_resource_name = '10.20.1.97'
vsphere.resource_pool_name = 'Provisioning'
vsphere.template_name = 'DevOps_Production_Templates/DevOps_Windows2008R2'
vsphere.name = 'TestBox'
vsphere.user = 'administrator'
vsphere.password = '************'
vsphere.insecure = 'false'
vsphere.data_store_name = 'QA-DS100'

end

end

end

Output is:

C:\vagrant-vsphere>vagrant provision TestBox
Updating Vagrant's berkshelf: 'C:/Users/DevOps_Admin/.berkshelf/TestBox/vagrant/
berkshelf-20140515-456-pdunpi-TestBox'
Resolving cookbook dependencies...
Using chef_handler (1.1.6)
Using windows (1.31.0)
Vendoring chef_handler (1.1.6) to C:/Users/DevOps_Admin/.berkshelf/TestBox/vagra
nt/berkshelf-20140515-456-pdunpi-TestBox/chef_handler
Vendoring windows (1.31.0) to C:/Users/DevOps_Admin/.berkshelf/TestBox/vagrant/b
erkshelf-20140515-456-pdunpi-TestBox/windows
==> TestBox: Warning! Folder sync disabled because the rsync binary is
==> TestBox: missing. Make sure rsync is installed and the binary can
==> TestBox: be found in PATH.
==> TestBox: Running provisioner: chef_solo...
Generating chef JSON and uploading...
==> TestBox: Running chef-solo...
==> TestBox: [2014-05-21T09:33:16-07:00] INFO: *** Chef 11.12.4 ***
==> TestBox: [2014-05-21T09:33:16-07:00] INFO: Chef-client pid: 1524
==> TestBox: [2014-05-21T09:33:45-07:00] INFO: Setting the run_list to ["recipe[
windows::TestRunBook]"] from CLI options
==> TestBox: [2014-05-21T09:33:45-07:00] INFO: Run List is [recipe[windows::Test
RunBook]]
==> TestBox: [2014-05-21T09:33:45-07:00] INFO: Run List expands to [windows::Tes
tRunBook]
==> TestBox: [2014-05-21T09:33:45-07:00] INFO: Starting Chef Run for Template-CI
.T-BX.COM
==> TestBox:
==> TestBox: [2014-05-21T09:33:45-07:00] INFO: Running start handlers
==> TestBox: [2014-05-21T09:33:45-07:00] INFO: Start handlers complete.
==> TestBox: [2014-05-21T09:33:46-07:00] INFO: WindowsPackage light-weight resou
rce already initialized -- overriding!
==> TestBox: [2014-05-21T09:33:48-07:00] INFO: Chef Run complete in 2.886037 sec
onds
==> TestBox: [2014-05-21T09:33:48-07:00] INFO: Running report handlers
==> TestBox: [2014-05-21T09:33:48-07:00] INFO: Report handlers complete

@mkuzmin
Copy link
Contributor

mkuzmin commented May 21, 2014

I believe this should be fixed as a part of #66
But I'm still solving issues in this pull request.

@StevenArmstrong
Copy link
Author

Thanks for the information.

@mkuzmin
Copy link
Contributor

mkuzmin commented Jul 8, 2014

PR #66 has been merged, but unfortunately NFS sync requires an additional piece of code, and it's not supported yet.

@mkuzmin
Copy link
Contributor

mkuzmin commented Aug 12, 2014

I've figured this issue out. There is nothing to fix in vagrant-vsphere plugin. There are two parts:

  1. RSync was selected because sync protocol should be explicitly configured in synced_folder_type property of Chef provisioner.
  2. Even if you select smb type, it will not work until adding smb sync folder implementation for windows guests addressing #3699 hashicorp/vagrant#4209 has been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants