'vagrant destroy' not working correctly in cygwin

[thasmo]

Hello there!

vagrant destroy
Vagrant is attempting to interface with the UI in a way that requires
a TTY. Most actions in Vagrant that require a TTY have configuration
switches to disable this requirement. Please do that or run Vagrant
with TTY.

That's on vagrant 1.2.1.

[thasmo]

'vagrant destroy --force' works.

[mitchellh]

Damn! Can you do me a favor and run a uname -s for me and tell me the output? (from cygwin)

[thasmo]

It is "CYGWIN_NT-6.2-WOW64" for my machine here at work (Windows 8).
Can get you the same later for Windows 7 at home, if you need it.

[thasmo]

For Windows 7 here it is "CYGWIN_NT-6.1-WOW64".

[mitchellh]

I'm unfortunately unable to reproduce this. Under Cygwin Vagrant works for me. Is this installed via the MSI installer?

[thasmo]

Oh, actually it is working right now on my PC at home, running Windows 7. Probably I'm not on Vagrant 1.2.1 on my PC at work. Sorry for any inconvinience - it seems to work with 1.2.1.

[oliver-dungey]

Maybe some more clues here ...

I am on Windows 7 64bit but uname -s returns CYGWIN_NT-6.1 without the WOW64 even though it is a 64bit cygwin install. This error only turned up after changing my configuration to turn on colorize (config.vm.provision.salt.tcolorize) - this error now comes up when trying to destroy existing VM's, --force fixes lets me destroy the VMs, removing tcolorize gets rid of the invalid configuration issue that seems to be hidden when calling destroy.

[russellvt]

As-per comments in the bug, above...setting the environment with "VAGRANT_DETECTED_OS=cygwin" is a good workaround, here.

[alfaburro]

the environment var worked for me.
uname-s CYGWIN_NT-10.0-WOW