[yast-commit] Build failed in Jenkins: yast-aytests-run-SLE12 » 2,autoyast #87
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/87/disp...
------------------------------------------
[...truncated 204.45 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/88/disp...
------------------------------------------
[...truncated 191.32 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/89/disp...
------------------------------------------
[...truncated 189.80 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/90/disp...
------------------------------------------
[...truncated 189.95 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/91/disp...
------------------------------------------
[...truncated 190.13 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/92/disp...
------------------------------------------
[...truncated 189.95 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/93/disp...
------------------------------------------
[...truncated 189.33 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/94/disp...
------------------------------------------
[...truncated 189.83 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
See https://ci.suse.de/job/yast-aytests-run-SLE12/GROUP=2,label=autoyast/95/disp...
------------------------------------------
[...truncated 188.41 KB...]
ERROR vagrant: The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:33:in `block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:235:in `block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/v2/command.rb:229:in `with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/ssh_config/command.rb:31:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FFFIgnoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
Ignoring ruby-libvirt-0.7.0 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.7.0
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR warden: Error occurred: Name `vagrant_autoyast_vm` of domain about to create is already taken. Please try to run
`vagrant up` command again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #
participants (1)
-
jenkins@suse.de