Ability to change or disable ControlMaster for Vagrant rsync

[kenorb]

Vagrant version

I'm using Vagrant 1.8.1

Host operating system & Guest operating system

Linux Ubuntu

Debug output

00:02:36.593 Command: rsync --verbose --archive --delete -z --copy-links --no-owner --no-group --rsync-path sudo rsync -e ssh -p 22 -o ControlMaster=auto -o ControlPath=/tmp/ssh.883 -o ControlPersist=10m -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i '/var/lib/jenkins/secrets/Key.pem' --exclude .vagrant/ /var/lib/jenkins/workspace/Test-VM/ ubuntu@54.224.37.17:/vagrant
00:02:36.593 Error: Warning: Permanently added '54.224.37.17' (ECDSA) to the list of known hosts.
00:02:36.593 Timeout, server 54.224.37.17 not responding.
00:02:36.593 mux_client_request_session: read from master failed: Broken pipe
00:02:36.593 Failed to connect to new control master
00:02:36.593 rsync: connection unexpectedly closed (0 bytes received so far) [sender]

Expected behavior

ControlMaster should be disabled based on the ~/.ssh/config settings which are:

Host *
  ControlMaster no
  ControlPath none

However these settings are ignored.

Actual behavior

The ControlMaster is still set to auto are per rsync command above.

Steps to reproduce

Ideally Vagrant should use the same settings are per user SSH config file, but I think it's not. Same for other settings such as ControlPath which may fail sometimes for rsync, so I'd like to get rid of these settings or change them, as /tmp is not a good place to keep them anyway (as per this post). This is also to avoid issues as described in GH-6702 (but my both machines are Linux).

I'm using Vagrant AWS provider.

Workaround

The workaround is to comment out this line:

control_options = "-o ControlMaster=auto -o ControlPath=#{controlpath} -o ControlPersist=10m "

from helper.rb file. Although in my 1.8.1 I've got 3 lines to comment out.

[kenorb]

Actually it wasn't the problem of ControlMaster. Don't need to disable it anymore.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.