Last active
January 4, 2016 10:29
-
-
Save atomic-penguin/8609521 to your computer and use it in GitHub Desktop.
test-kitchen-failure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [jenkins@ci mu-jenkins-kitchen]$ kitchen converge default-centos-64 -l debug | |
| -----> Starting Kitchen (v1.1.1) | |
| D [kitchen::driver::vagrant command] BEGIN (vagrant --version) | |
| D [kitchen::driver::vagrant command] END (0m0.33s) | |
| -----> Creating <default-centos-64>... | |
| D <default-centos-64> is synchronizing on Kitchen::Driver::Vagrant#create | |
| D <default-centos-64> is messaging Kitchen::Driver::Vagrant#create | |
| D Creating Vagrantfile for <default-centos-64> (/var/lib/jenkins/workspace/mu-jenkins-kitchen/.kitchen/kitchen-vagrant/default-centos-64/Vagrantfile) | |
| D ------------ | |
| D Vagrant.configure("2") do |c| | |
| D c.vm.box = "opscode-centos-6.4" | |
| D c.vm.box_url = "https://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_centos-6.4_chef-provisionerless.box" | |
| D c.vm.hostname = "default-centos-64.vagrantup.com" | |
| D c.vm.synced_folder ".", "/vagrant", disabled: true | |
| D c.vm.provider :virtualbox do |p| | |
| D p.customize ["modifyvm", :id, "--memory", "256"] | |
| D end | |
| D end | |
| D ------------ | |
| D [kitchen::driver::vagrant command] BEGIN (vagrant up --no-provision --provider=virtualbox) | |
| Bringing machine 'default' up with 'virtualbox' provider... | |
| [default] Clearing any previously set forwarded ports... | |
| [Berkshelf] Skipping Berkshelf with --no-provision | |
| [default] Clearing any previously set network interfaces... | |
| [default] Preparing network interfaces based on configuration... | |
| [default] Forwarding ports... | |
| [default] -- 22 => 2222 (adapter 1) | |
| [default] Running 'pre-boot' VM customizations... | |
| [default] Booting VM... | |
| [default] Waiting for machine to boot. This may take a few minutes... | |
| D [kitchen::driver::vagrant command] END (5m8.82s) | |
| >>>>>> ------Exception------- | |
| >>>>>> Class: Kitchen::ActionFailed | |
| >>>>>> 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] Clearing any previously set forwarded ports... | |
| [Berkshelf] Skipping Berkshelf with --no-provision | |
| [default] Clearing any previously set network interfaces... | |
| [default] Preparing network interfaces based on configuration... | |
| [default] Forwarding ports... | |
| [default] -- 22 => 2222 (adapter 1) | |
| [default] Running 'pre-boot' VM customizations... | |
| [default] Booting VM... | |
| [default] Waiting for machine to boot. This may take a few minutes... | |
| 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. This can | |
| mean a number of things. | |
| 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] | |
| >>>>>> ---------------------- | |
| >>>>>> Please see .kitchen/logs/kitchen.log for more details | |
| D ------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] Clearing any previously set forwarded ports... | |
| [Berkshelf] Skipping Berkshelf with --no-provision | |
| [default] Clearing any previously set network interfaces... | |
| [default] Preparing network interfaces based on configuration... | |
| [default] Forwarding ports... | |
| [default] -- 22 => 2222 (adapter 1) | |
| [default] Running 'pre-boot' VM customizations... | |
| [default] Booting VM... | |
| [default] Waiting for machine to boot. This may take a few minutes... | |
| 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. This can | |
| mean a number of things. | |
| 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 ---Nested Exception--- | |
| D Class: Kitchen::ShellOut::ShellCommandFailed | |
| D Message: 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] Clearing any previously set forwarded ports... | |
| [Berkshelf] Skipping Berkshelf with --no-provision | |
| [default] Clearing any previously set network interfaces... | |
| [default] Preparing network interfaces based on configuration... | |
| [default] Forwarding ports... | |
| [default] -- 22 => 2222 (adapter 1) | |
| [default] Running 'pre-boot' VM customizations... | |
| [default] Booting VM... | |
| [default] Waiting for machine to boot. This may take a few minutes... | |
| 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. This can | |
| mean a number of things. | |
| 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 ------Backtrace------- | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/shell_out.rb:70:in `rescue in run_command' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/shell_out.rb:59:in `run_command' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/driver/base.rb:158:in `run_command' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/kitchen-vagrant-0.14.0/lib/kitchen/driver/vagrant.rb:123:in `run' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/kitchen-vagrant-0.14.0/lib/kitchen/driver/vagrant.rb:68:in `create' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:273:in `public_send' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:273:in `block in perform_action' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:305:in `call' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:305:in `block in synchronize_or_call' | |
| D <internal:prelude>:10:in `synchronize' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:303:in `synchronize_or_call' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:283:in `block in action' | |
| D /var/lib/jenkins/lib/ruby/1.9.1/benchmark.rb:280:in `measure' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:282:in `action' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:273:in `perform_action' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:252:in `create_action' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:246:in `block in transition_to' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:245:in `each' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:245:in `transition_to' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/instance.rb:119:in `converge' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/cli.rb:314:in `public_send' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/cli.rb:314:in `block in run_serial' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/cli.rb:314:in `map' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/cli.rb:314:in `run_serial' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/cli.rb:308:in `block in exec_action' | |
| D /var/lib/jenkins/lib/ruby/1.9.1/benchmark.rb:280:in `measure' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/cli.rb:305:in `exec_action' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/cli.rb:108:in `block (2 levels) in <class:CLI>' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/thor-0.18.1/lib/thor/command.rb:27:in `run' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/thor-0.18.1/lib/thor/invocation.rb:120:in `invoke_command' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/cli.rb:288:in `invoke_task' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/thor-0.18.1/lib/thor.rb:363:in `dispatch' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/thor-0.18.1/lib/thor/base.rb:439:in `start' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/bin/kitchen:13:in `block in <top (required)>' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/lib/kitchen/errors.rb:81:in `with_friendly_errors' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/gems/test-kitchen-1.1.1/bin/kitchen:13:in `<top (required)>' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/bin/kitchen:23:in `load' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/bin/kitchen:23:in `<main>' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `eval' | |
| D /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `<main>' | |
| D ---------------------- |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello
My name is miss naomi,
I saw your profile today and feel more interest to contact you,please write to me via(naomiwilliam2@hotmail.com)for me to send you my ^pictures and introduce myself to you i am waiting for your mail thanks.