Issue while executing kitchen create from Jenkins

Hi All,

I am trying to automate chef workflow using Jenkins and blocked at the st stage itself.
I am trying to run kitchen create from Jenkins project using build as Windows batch file as

===
echo "This the is batch script for execution of kitchen"
set root=J:\Chef\learn-chef\cookbooks\motd
cd /d %root%
kitchen create

While executing build from jenkins I could see below message

===
Started by user admin
Building in workspace C:\Program Files (x86)\Jenkins\workspace\motd_test
[motd_test] $ cmd /c call C:\Windows\TEMP\hudson9042715592821301628.bat

C:\Program Files (x86)\Jenkins\workspace\motd_test>echo “This the is batch script for execution of kitchen”
“This the is batch script for execution of kitchen”

C:\Program Files (x86)\Jenkins\workspace\motd_test>set root=J:\Chef\learn-chef\cookbooks\motd

C:\Program Files (x86)\Jenkins\workspace\motd_test>cd /d J:\Chef\learn-chef\cookbooks\motd

J:\Chef\learn-chef\cookbooks\motd>kitchen create
-----> Starting Kitchen (v1.10.2)
-----> Creating …
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Box ‘bento/centos-7.2’ could not be found. Attempting to find and install…
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'bento/centos-7.2’
default: URL: https://atlas.hashicorp.com/bento/centos-7.2
==> default: Adding box ‘bento/centos-7.2’ (v2.3.0) for provider: virtualbox
default: Downloading: https://atlas.hashicorp.com/bento/boxes/centos-7.2/versions/2.3.0/providers/virtualbox.box
==> default: Box download is resuming from prior download progress

After above message it is not moving forward, I have waited for nearly 2 hours.
But at the same time if I run the same batch script outside of Jenkins from the same machine it works perfectly fine with below message

===
-----> Starting Kitchen (v1.10.2)
-----> Creating …
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Importing base box ‘bento/centos-7.2’…
==> default: Matching MAC address for NAT networking…
==> default: Checking if box ‘bento/centos-7.2’ is up to date…
==> default: A newer version of the box ‘bento/centos-7.2’ is available!
You currently
==> default: have version ‘2.2.9’. The latest is version ‘2.3.0’. Run
==> default: vagrant box update to update.
==> default: Setting the name of the VM: kitchen-motd-default-centos-72_d
efault_1476283362339_30482
==> default: Fixed port collision for 22 => 2222. Now on port 2202.
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
==> default: Forwarding ports…
default: 22 (guest) => 2202 (host) (adapter 1)
==> default: Booting VM…
==> default: Waiting for machine to boot. This may take a few minutes…
default: SSH address: 127.0.0.1:2202
default: SSH username: vagrant
default: SSH auth method: private key
default:
default: Vagrant insecure key detected. Vagrant will automatically re
place
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest…
default: Removing insecure key from the guest if it’s present…
default: Key inserted! Disconnecting and reconnecting using new SSH k
ey…
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM…
==> default: Setting hostname…
==> default: Machine not provisioned because --no-provision is specifie
d.
[SSH] Established
Vagrant instance created.
Finished creating (2m10.59s).
-----> Kitchen is finished. (2m23.33s)

===

Could anyone please help me to get this resolved?

Thanks and Regards,
Pankaj

Hi All,

Any help is much appreciated.

Thanks and Regards,
Pankaj

Can you elaborate on what the problem is? You ran kitchen create and it appears to have succeeded. Maybe you meant to run kitchen test instead and have it actually run your recipes?

Hi Matt,

Thanks.
Actually I an trying to run kitchen create using Jenkins and it is not successful.
It just stops at below
J:\Chef\learn-chef\cookbooks\motd>kitchen create
-----> Starting Kitchen (v1.10.2)
-----> Creating …
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Box ‘bento/centos-7.2’ could not be found. Attempting to find and install…
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'bento/centos-7.2’
default: URL: https://atlas.hashicorp.com/bento/centos-7.2
==> default: Adding box ‘bento/centos-7.2’ (v2.3.0) for provider: virtualbox
default: Downloading: https://atlas.hashicorp.com/bento/boxes/centos-7.2/versions/2.3.0/providers/virtualbox.box
==> default: Box download is resuming from prior download progress
===
It is not moving ahead after above line.

But when I am running the kitchen create from the same machine outside of jenkins i.e. executing kitchen create command from chef Dk power shell it is working.

So I am trying to solve why the job from jenkins running command kitchen create not working and if you see the message also it is showing different when I am running through Jenkins.

Thanks and Regards,
Pankaj

Ahh. So sorry I missed that in your original post. One thing to try is adding -l debug to get debugging info.

Hi Matt,

Sure I will add -l debug to kitchen and see.
Also Can I send you the plan of the system which I am trying to setup using jenkins and Chef and you can tell me whether that is correct approach or not?
So that I can avoid issue like above?

Thanks and Regards,
Pankaj

sure.

Thanks Matt. I will send you the debug first and then will send you the plan.

-----> Creating …
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Importing base box ‘bento/centos-7.2’…
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

   Command: ["import", "-n", "C:/Windows/System32/config/systemprofile/.vagrant.d/boxes/bento-VAGRANTSLASH-centos-7.2/2.3.0/virtualbox/box.ovf"]
   
   Stderr: 0%...

   Progress state: VBOX_E_FILE_ERROR

   VBoxManage.exe: error: Appliance read failed

   VBoxManage.exe: error: Could not read OVF file 'box.ovf' (VERR_PATH_NOT_FOUND)

   VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance

   VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)" at line 307 of file VBoxManageAppliance.cpp

------Exception-------
Class: Kitchen::ActionFailed
Message: 1 actions failed.
Failed to complete #create action: [Expected process to exit with [0], but received ‘1’
---- Begin output of vagrant up --no-provision --provider virtualbox ----
STDOUT: Bringing machine ‘default’ up with ‘virtualbox’ provider…

==> default: Importing base box ‘bento/centos-7.2’…
STDERR: There was an error while executing VBoxManage, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: [“import”, “-n”, “C:/Windows/System32/config/systemprofile/.vagrant.d/boxes/bento-VAGRANTSLASH-centos-7.2/2.3.0/virtualbox/box.ovf”]

Stderr: 0%…

Progress state: VBOX_E_FILE_ERROR

VBoxManage.exe: error: Appliance read failed

VBoxManage.exe: error: Could not read OVF file ‘box.ovf’ (VERR_PATH_NOT_FOUND)

VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance

VBoxManage.exe: error: Context: “enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)” at line 307 of file VBoxManageAppliance.cpp
---- End output of vagrant up --no-provision --provider virtualbox ----
Ran vagrant up --no-provision --provider virtualbox returned 1] on default-centos-72


Please see .kitchen/logs/kitchen.log for more details
Also try running kitchen diagnose --all for configuration
Build step ‘Execute Windows batch command’ marked build as failure
Finished: FAILURE

Hi Matt,

Below is the objective and action plan

Objective : Create a auto deply pipeline for software on Servers

  1. 3 different environments : Dev,UAT and Prod
  2. Git will be used as version control repo for cookbooks.
  3. Devops engineer will write coookbook and will test using vagrant locally for successful execution.
    lint,unit testing will be done at this point.
  4. Once success tagging will be done to the branch in git and this will trigger jenkins job. This job will upload cookbooks
    to Chef server. On success of this job new job will trigger which will bootstrap node based on cookbook environment.
  5. On successful Integration test suit will be executed along with performance test.
  6. after successful UAT server will be bootstrapped and all above tests will be executed.
  7. After successful completion of above manual execution of production server bootstrap will happen followed by Integration and performance testing.

Could you please tell me what is the best way or above plan is good to achieve?
We need to install our custom software on different environment periodically and test it.

Thanks and Regards,
Pankaj

Hi Matt,

Could you please check above and let me know your thoughts?

Thanks and Regards,

That certainly looks like a sensible action plan. I’d encourage you to have a look at chef automate. While its not free, maintaining your own custom Jenkins pipeline is also very expensive.

Seems like the user running Jenkins does not have rights to read the ovf file... Rights you have when running the command.

I place a bet Jenkins is launched as local system, and so have a far different hole directory than you have. Create a correct user to run Jenkins service, and prepare the env (virtual box and kitchen) logged on with this user and you'll solve your problem.

Thanks for suggestion Matt. Let me check with management what we can do regarding this.

Hi Tansibai,

Thanks. I found that the folder C:/Windows/System32/config/systemprofile/.vagrant.d was not present at the path so I have copied the .vagrant.d folder from sysWOW64.

Now it is moving ahead but not proceeding after below line

D [Vagrant command] BEGIN (vagrant up --no-provision --provider virtualbox)
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Checking if box ‘bento/centos-7.2’ is up to date…
==> default: Clearing any previously set forwarded ports…
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
==> default: Forwarding ports…
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM…
==> default: Waiting for machine to boot. This may take a few minutes…
** default: SSH address: 127.0.0.1:2222**
** default: SSH username: vagrant**
** default: SSH auth method: private key**

I have created the same user in jenkins which I am using on the on the workstation as well but not moving ahead.

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured (“config.vm.boot_timeout” value) time period.

   If you look above, you should be able to see the error(s) that
   Vagrant had when attempting to connect to the machine. These errors
   are usually good hints as to what may be wrong.
   
   If you're using a custom box, make sure that networking is properly
   working and you're able to connect to the machine. It is a common
   problem that networking isn't setup properly in these boxes.
   Verify that authentication configurations are also setup properly,
   as well.
   
   If the box appears to be booting properly, you may want to increase
   the timeout ("config.vm.boot_timeout") value.

D [Vagrant command] END (0m0.00s)

------Exception-------
Class: Kitchen::ActionFailed
Message: 1 actions failed.
Failed to complete #create action: [Expected process to exit with [0], but received ‘1’
---- Begin output of vagrant up --no-provision --provider virtualbox ----
STDOUT: Bringing machine ‘default’ up with ‘virtualbox’ provider…

==> default: Checking if box ‘bento/centos-7.2’ is up to date…

==> default: Clearing any previously set forwarded ports…

==> default: Clearing any previously set network interfaces…

==> default: Preparing network interfaces based on configuration…

default: Adapter 1: nat

==> default: Forwarding ports…

default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Booting VM…

==> default: Waiting for machine to boot. This may take a few minutes…

default: SSH address: 127.0.0.1:2222

default: SSH username: vagrant

default: SSH auth method: private key

STDERR: Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured (“config.vm.boot_timeout” value) time period.

If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.

If you’re using a custom box, make sure that networking is properly

working and you’re able to connect to the machine. It is a common

problem that networking isn’t setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.

If the box appears to be booting properly, you may want to increase

the timeout (“config.vm.boot_timeout”) value.
---- End output of vagrant up --no-provision --provider virtualbox ----
Ran vagrant up --no-provision --provider virtualbox returned 1] on default-centos-72


Please see .kitchen/logs/kitchen.log for more details
Also try running kitchen diagnose --all for configuration
D ------Exception-------
D Class: Kitchen::ActionFailed
D Message: 1 actions failed.

Failed to complete #create action: [Expected process to exit with [0], but received '1'

---- Begin output of vagrant up --no-provision --provider virtualbox ----
STDOUT: Bringing machine ‘default’ up with ‘virtualbox’ provider…

==> default: Checking if box ‘bento/centos-7.2’ is up to date…

==> default: Clearing any previously set forwarded ports…

==> default: Clearing any previously set network interfaces…

==> default: Preparing network interfaces based on configuration…

default: Adapter 1: nat

==> default: Forwarding ports…

default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Booting VM…

==> default: Waiting for machine to boot. This may take a few minutes…

default: SSH address: 127.0.0.1:2222

default: SSH username: vagrant

default: SSH auth method: private key

STDERR: Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured (“config.vm.boot_timeout” value) time period.

If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.

If you’re using a custom box, make sure that networking is properly

working and you’re able to connect to the machine. It is a common

problem that networking isn’t setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.

If the box appears to be booting properly, you may want to increase

the timeout (“config.vm.boot_timeout”) value.
---- End output of vagrant up --no-provision --provider virtualbox ----
Ran vagrant up --no-provision --provider virtualbox returned 1] on default-centos-72
D ----------------------
D ------Backtrace-------
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command.rb:187:in report_errors' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command.rb:178:inrun_action’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command/action.rb:39:in block in call' D C:/opscode/chefdk/embedded/lib/ruby/2.1.0/benchmark.rb:279:inmeasure’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command/action.rb:37:in call' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/cli.rb:56:inperform’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/cli.rb:184:in block (2 levels) in <class:CLI>' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:inrun’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in invoke_command' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/cli.rb:325:ininvoke_task’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in dispatch' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:instart’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/bin/kitchen:13:in block in <top (required)>' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/errors.rb:174:inwith_friendly_errors’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/bin/kitchen:13:in <top (required)>' D C:/opscode/chefdk/bin/kitchen:20:inload’
D C:/opscode/chefdk/bin/kitchen:20:in `'
D ----End Backtrace-----
D -Composite Exception–
D Class: Kitchen::ActionFailed
D Message: Failed to complete #create action: [Expected process to exit with [0], but received ‘1’
---- Begin output of vagrant up --no-provision --provider virtualbox ----
STDOUT: Bringing machine ‘default’ up with ‘virtualbox’ provider…

==> default: Checking if box ‘bento/centos-7.2’ is up to date…

==> default: Clearing any previously set forwarded ports…

==> default: Clearing any previously set network interfaces…

==> default: Preparing network interfaces based on configuration…

default: Adapter 1: nat

==> default: Forwarding ports…

default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Booting VM…

==> default: Waiting for machine to boot. This may take a few minutes…

default: SSH address: 127.0.0.1:2222

default: SSH username: vagrant

default: SSH auth method: private key

STDERR: Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured (“config.vm.boot_timeout” value) time period.

If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.

If you’re using a custom box, make sure that networking is properly

working and you’re able to connect to the machine. It is a common

problem that networking isn’t setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.

If the box appears to be booting properly, you may want to increase

the timeout (“config.vm.boot_timeout”) value.
---- End output of vagrant up --no-provision --provider virtualbox ----
Ran vagrant up --no-provision --provider virtualbox returned 1] on default-centos-72
D ----------------------
D ------Backtrace-------
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/shell_out.rb:73:in rescue in run_command' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/shell_out.rb:61:inrun_command’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/kitchen-vagrant-0.20.0/lib/kitchen/driver/vagrant.rb:343:in run_command' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/kitchen-vagrant-0.20.0/lib/kitchen/driver/vagrant.rb:302:inrun’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/kitchen-vagrant-0.20.0/lib/kitchen/driver/vagrant.rb:373:in run_vagrant_up' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/kitchen-vagrant-0.20.0/lib/kitchen/driver/vagrant.rb:96:increate’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:449:in public_send' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:449:inblock in perform_action’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:510:in call' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:510:inblock in synchronize_or_call’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:508:in synchronize' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:508:insynchronize_or_call’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:478:in block in action' D C:/opscode/chefdk/embedded/lib/ruby/2.1.0/benchmark.rb:279:inmeasure’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:477:in action' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:449:inperform_action’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:359:in create_action' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:348:inblock in transition_to’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:347:in each' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:347:intransition_to’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:127:in create' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command.rb:201:inpublic_send’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command.rb:201:in run_action_in_thread' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command.rb:173:inblock (2 levels) in run_action’
D ----End Backtrace-----
D —Nested Exception—
D Class: Kitchen::ActionFailed
D Message: Failed to complete #create action: [Expected process to exit with [0], but received ‘1’
---- Begin output of vagrant up --no-provision --provider virtualbox ----
STDOUT: Bringing machine ‘default’ up with ‘virtualbox’ provider…

==> default: Checking if box ‘bento/centos-7.2’ is up to date…

==> default: Clearing any previously set forwarded ports…

==> default: Clearing any previously set network interfaces…

==> default: Preparing network interfaces based on configuration…

default: Adapter 1: nat

==> default: Forwarding ports…

default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Booting VM…

==> default: Waiting for machine to boot. This may take a few minutes…

default: SSH address: 127.0.0.1:2222

default: SSH username: vagrant

default: SSH auth method: private key

STDERR: Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured (“config.vm.boot_timeout” value) time period.

If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.

If you’re using a custom box, make sure that networking is properly

working and you’re able to connect to the machine. It is a common

problem that networking isn’t setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.

If the box appears to be booting properly, you may want to increase

the timeout (“config.vm.boot_timeout”) value.
---- End output of vagrant up --no-provision --provider virtualbox ----
Ran vagrant up --no-provision --provider virtualbox returned 1]
D ----------------------
D ------Backtrace-------
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/shell_out.rb:73:in rescue in run_command' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/shell_out.rb:61:inrun_command’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/kitchen-vagrant-0.20.0/lib/kitchen/driver/vagrant.rb:343:in run_command' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/kitchen-vagrant-0.20.0/lib/kitchen/driver/vagrant.rb:302:inrun’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/kitchen-vagrant-0.20.0/lib/kitchen/driver/vagrant.rb:373:in run_vagrant_up' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/kitchen-vagrant-0.20.0/lib/kitchen/driver/vagrant.rb:96:increate’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:449:in public_send' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:449:inblock in perform_action’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:510:in call' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:510:inblock in synchronize_or_call’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:508:in synchronize' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:508:insynchronize_or_call’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:478:in block in action' D C:/opscode/chefdk/embedded/lib/ruby/2.1.0/benchmark.rb:279:inmeasure’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:477:in action' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:449:inperform_action’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:359:in create_action' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:348:inblock in transition_to’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:347:in each' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:347:intransition_to’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/instance.rb:127:in create' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command.rb:201:inpublic_send’
D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command.rb:201:in run_action_in_thread' D C:/opscode/chefdk/embedded/lib/ruby/gems/2.1.0/gems/test-kitchen-1.10.2/lib/kitchen/command.rb:173:inblock (2 levels) in run_action’
D ----End Backtrace-----
Build step ‘Execute Windows batch command’ marked build as failure
Finished: FAILUR

Could you please help?