Two config.ssh.pty setting issues with Cloud provisioners

[VMTrooper]

Hello Team,

Here is my Vagrantfile: http://pastebin.com/PBtDSAt8

Issue 1: config.ssh.pty setting is applied globally despite using conditional statements

• There is a problem with config.ssh.pty = true for Ubuntu VMs as noted in the issue below.
• I tried to put in an If statement so that the value is only set to true for the CentOS VM that is complaining about tty during Rsync
• The conditional statement is ignored and the setting is true for all VMs, which leads to issue 2...
• Honestly, I'm not sure if it is possible for config.* settings to be controlled by conditional statements. Apologies if that's an expected behavior.

Issue 2: "true" setting for Ubuntu VMs leaves the VM hanging indefinitely after shell provisioner completes

• I have waited up to 10 minutes for the shell provisioner to exit out and move on to the next VM, but it never does.

As a workaround, I'm currently instantiating VMs one-at-a-time and editing the Vagrantfile between each VM boot.

Let me know if you have any further questions,
Trevor

[mitchellh]

For the first issue, you must not set it on the global config, you must set it on the node config directly.

I'll try to repro the second.

[VMTrooper]

didn't realize that the setting could be local. Thanks! Issue #1 got cleared up when I changed the code to be per box variable that I defined.

Issue #2 is not as critical considering that I can use conditional statements, but it would be nice to address or at least document in case anyone runs into a corner case

[mitchellh]

I'm unable to reproduce the second issue with my shell script. Let me know if you have a simple repro case and i'll take a look.

[VMTrooper]

Thanks Mitchell. I will try again and post a Vagrantfile that can reproduce the condition.

On Dec 30, 2013, at 3:44 PM, Mitchell Hashimoto notifications@github.com wrote:

I'm unable to reproduce the second issue with my shell script. Let me know if you have a simple repro case and i'll take a look.

—
Reply to this email directly or view it on GitHub.