It looks like chef is being called thusly:
D [WinRM]
plaintext::http://redacted.ip.address:5985/wsman<{:disable_sspi=>true,
:basic_auth_only=>true, :user=>"vagrant", :pass=>"redacted"}> (
$env:PATH = [System.Environment]::GetEnvironmentVariable("PATH","Machine")
& $env:systemdrive\opsc
I'd have to look at the code, but IIRC doesn't test-kitchen use its own
communicator to execute Chef? If so, then I doubt test-kitchen wraps Chef
execution in a scheduled task like Vagrant does. Directly installing SQL
Server over WinRM without breaking out of the process via a scheduled task
does
Thanks for looking at this, we really appreciate it.
We are building inside test kitchen, this is the Vagrantfile being
generated by test kitchen:
Vagrant.configure("2") do |c|
c.berkshelf.enabled = false if Vagrant.has_plugin?("vagrant-berkshelf")
c.vm.box = "local/windows-2008-r2-sp1-x64
That's odd, I've had SQL Server 2008 R2 installing on Vagrant boxes via
Chef for a while now without any issues. I just checked my CI build for our
SQL Server cookbook and its running fine through Vagrant 1.6.5 and our
custom Packer build that uses WinRM. Mind sharing your Vagrantfile?
On Frid
