Mailinglist Archive: yast-commit (977 mails)

< Previous Next >
[yast-commit] Build failed in Jenkins: yast-aytests-run » 0,autoyast #299
  • From: jenkins@xxxxxxx
  • Date: Mon, 2 Jan 2017 18:36:29 +0100 (CET)
  • Message-id: <-649135739.3581.1483378589462.JavaMail.jenkins@ci>
https://ci.suse.de/job/yast-aytests-run/GROUP=0,label=autoyast/299/------------------------------------------
[...truncated 278.71 KB...]
vagrant box add 'autoyast'
'<https://ci.suse.de/job/yast-aytests-run/GROUP=0,label=autoyast/ws/aytests-workspace/autoyast.box'>

To use it:
vagrant init 'autoyast'
vagrant up --provider=libvirt
vagrant ssh
I, [2017-01-02T18:36:12.260510 #20669] INFO -- : Importing kvm image into
Vagrant
WARN environment: No local data path is set. Local data cannot be stored.
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'autoyast' (v0) for provider:
box: Unpacking necessary files from:
file://<https://ci.suse.de/job/yast-aytests-run/GROUP=0,label=autoyast/ws/aytests-workspace/autoyast.box>
 box: Progress: 0% (Rate: 0/s, Estimated time remaining: --:--:--)
box: Progress: 35% (Rate: 1140M/s, Estimated time remaining: --:--:--)==>
box: Successfully added box 'autoyast' (v0) for 'libvirt'!
error: failed to get vol 'autoyast_vagrant_box_image_0.img'
error: Storage volume not found: no storage vol with matching path
'autoyast_vagrant_box_image_0.img'

WARN environment: Process-lock in use:
machine-action-b4568cfdf95e72ad3ba23419c8fa33ee
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::MachineActionLockedError: An action 'destroy'
was attempted on the machine 'autoyast_vm',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.

If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.>
ERROR vagrant: An action 'destroy' was attempted on the machine 'autoyast_vm',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.

If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.
ERROR vagrant:
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:194:in
`rescue in action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:154:in
`action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/command.rb:31:in
`block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:226:in
`block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:220:in
`each'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:220:in
`with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/command.rb:30:in
`execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:301:in
`cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant:174:in `<main>'
An action 'destroy' was attempted on the machine 'autoyast_vm',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.

If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.
Bringing machine 'autoyast_vm' up with 'libvirt' provider...
WARN environment: Process-lock in use:
machine-action-b4568cfdf95e72ad3ba23419c8fa33ee
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::MachineActionLockedError: An action 'up' was
attempted on the machine 'autoyast_vm',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.

If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.>
ERROR vagrant: An action 'up' was attempted on the machine 'autoyast_vm',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.

If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.
ERROR vagrant:
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:194:in
`rescue in action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:154:in
`action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in
`block (2 levels) in run'
An action 'up' was attempted on the machine 'autoyast_vm',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.

If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::SSHNotReady: 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: 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.7.4/plugins/commands/ssh_config/command.rb:33:in
`block in execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:226:in
`block in with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:220:in
`each'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/plugin/v2/command.rb:220:in
`with_target_vms'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/command.rb:31:in
`execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/cli.rb:42:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:301:in
`cli'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant:174: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.
==> autoyast_vm: Domain is not created. Please run `vagrant up` first.
FF
An error occurred in an `after(:context)` hook.
Net::SSH::Simple::Error: getaddrinfo: Name or service not known @
#<Net::SSH::Simple::Result exception=#<SocketError: getaddrinfo: Name or
service not known> finish_at=2017-01-02 18:36:29 +0100 stderr="" stdout=""
success=false>
occurred at
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:632:in
`rescue in with_session'



Failures:

1) SLES 12 with all yast2 packages installed check generated AutoYaST
profile (bsc#954412)
Failure/Error: raise Net::SSH::Simple::Error, [e, @result]

Net::SSH::Simple::Error:
getaddrinfo: Name or service not known @ #<Net::SSH::Simple::Result
cmd=:upload exception=#<SocketError: getaddrinfo: Name or service not known>
finish_at=2017-01-02 18:36:29 +0100 host="autoyast_vm" last_event_at=2017-01-02
18:36:28 +0100 op=:scp
opts={:config=>#<Pathname:<https://ci.suse.de/job/yast-aytests-run/GROUP=0,label=autoyast/ws/aytests-workspace/vagrant/config.ssh>,>

:scp_src=>"<https://ci.suse.de/job/yast-aytests-run/GROUP=0,label=autoyast/ws/aytests/check_schema.sh";,>
:scp_dst=>"/tmp/check_schema.sh", :timeout=>60, :operation_timeout=>3600,
:close_timeout=>5, :keepalive_interval=>60} start_at=2017-01-02 18:36:28 +0100
stderr="" stdout="" success=false>
Shared Example Group: "test_scripts" called from ./sles12_all_yast.rb:4
#
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:632:in
`rescue in with_session'
#
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:618:in
`with_session'
#
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:658:in
`scp'
#
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:338:in
`scp_put'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/vagrant_runner.rb:54:in
`block in run'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/vagrant_runner.rb:92:in
`with_conn'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/vagrant_runner.rb:52:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/test_helpers.rb:54:in
`remote_run_test_script'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/test_helpers.rb:42:in
`run_test_script'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/spec_helper.rb:51:in
`block (3 levels) in <top (required)>'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:252:in
`instance_exec'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:252:in
`block in run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:494:in
`block in with_around_and_singleton_context_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:451:in
`block in with_around_example_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/hooks.rb:471:in
`block in run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/hooks.rb:609:in
`run_around_example_hooks_for'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/hooks.rb:471:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:451:in
`with_around_example_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:494:in
`with_around_and_singleton_context_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:249:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example_group.rb:627:in
`block in run_examples'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example_group.rb:623:in
`map'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example_group.rb:623:in
`run_examples'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example_group.rb:589:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:113:in
`block (3 levels) in run_specs'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:113:in
`map'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:113:in
`block (2 levels) in run_specs'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/configuration.rb:1836:in
`with_suite_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:112:in
`block in run_specs'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/reporter.rb:77:in
`report'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:111:in
`run_specs'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:87:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:71:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:45:in
`invoke'
# /usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/exe/rspec:4:in `<top
(required)>'
# /usr/bin/rspec:23:in `load'
# /usr/bin/rspec:23:in `<main>'
#
# Showing full backtrace because every line was filtered out.
# See docs for RSpec::Configuration#backtrace_exclusion_patterns and
# RSpec::Configuration#backtrace_inclusion_patterns for more information.
# ------------------
# --- Caused by: ---
# SocketError:
# getaddrinfo: Name or service not known
# /usr/lib64/ruby/2.1.0/socket.rb:232:in `getaddrinfo'

2) SLES 12 with all yast2 packages installed password are set (bsc#973639,
bsc#974220, bsc#971804 and bsc#965852)
Failure/Error: raise Net::SSH::Simple::Error, [e, @result]

Net::SSH::Simple::Error:
getaddrinfo: Name or service not known @ #<Net::SSH::Simple::Result
cmd=:upload exception=#<SocketError: getaddrinfo: Name or service not known>
finish_at=2017-01-02 18:36:29 +0100 host="autoyast_vm" last_event_at=2017-01-02
18:36:29 +0100 op=:scp
opts={:config=>#<Pathname:<https://ci.suse.de/job/yast-aytests-run/GROUP=0,label=autoyast/ws/aytests-workspace/vagrant/config.ssh>,>

:scp_src=>"<https://ci.suse.de/job/yast-aytests-run/GROUP=0,label=autoyast/ws/aytests/set_passwords.sh";,>
:scp_dst=>"/tmp/set_passwords.sh", :timeout=>60, :operation_timeout=>3600,
:close_timeout=>5, :keepalive_interval=>60} start_at=2017-01-02 18:36:29 +0100
stderr="" stdout="" success=false>
Shared Example Group: "test_scripts" called from ./sles12_all_yast.rb:4
#
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:632:in
`rescue in with_session'
#
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:618:in
`with_session'
#
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:658:in
`scp'
#
/usr/lib64/ruby/gems/2.1.0/gems/net-ssh-simple-1.6.16/lib/net/ssh/simple.rb:338:in
`scp_put'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/vagrant_runner.rb:54:in
`block in run'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/vagrant_runner.rb:92:in
`with_conn'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/vagrant_runner.rb:52:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/test_helpers.rb:54:in
`remote_run_test_script'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/test_helpers.rb:42:in
`run_test_script'
#
/usr/lib64/ruby/gems/2.1.0/gems/aytests-1.0.29/lib/aytests/spec_helper.rb:51:in
`block (3 levels) in <top (required)>'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:252:in
`instance_exec'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:252:in
`block in run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:494:in
`block in with_around_and_singleton_context_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:451:in
`block in with_around_example_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/hooks.rb:471:in
`block in run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/hooks.rb:609:in
`run_around_example_hooks_for'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/hooks.rb:471:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:451:in
`with_around_example_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:494:in
`with_around_and_singleton_context_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example.rb:249:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example_group.rb:627:in
`block in run_examples'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example_group.rb:623:in
`map'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example_group.rb:623:in
`run_examples'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/example_group.rb:589:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:113:in
`block (3 levels) in run_specs'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:113:in
`map'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:113:in
`block (2 levels) in run_specs'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/configuration.rb:1836:in
`with_suite_hooks'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:112:in
`block in run_specs'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/reporter.rb:77:in
`report'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:111:in
`run_specs'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:87:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:71:in
`run'
#
/usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/lib/rspec/core/runner.rb:45:in
`invoke'
# /usr/lib64/ruby/gems/2.1.0/gems/rspec-core-3.5.1/exe/rspec:4:in `<top
(required)>'
# /usr/bin/rspec:23:in `load'
# /usr/bin/rspec:23:in `<main>'
#
# Showing full backtrace because every line was filtered out.
# See docs for RSpec::Configuration#backtrace_exclusion_patterns and
# RSpec::Configuration#backtrace_inclusion_patterns for more information.
# ------------------
# --- Caused by: ---
# SocketError:
# getaddrinfo: Name or service not known
# /usr/lib64/ruby/2.1.0/socket.rb:232:in `getaddrinfo'

Finished in 5.36 seconds (files took 0.30381 seconds to load)
2 examples, 2 failures

Failed examples:

rspec ./sles12_all_yast.rb[1:1] # SLES 12 with all yast2 packages installed
check generated AutoYaST profile (bsc#954412)
rspec ./sles12_all_yast.rb[1:2] # SLES 12 with all yast2 packages installed
password are set (bsc#973639, bsc#974220, bsc#971804 and bsc#965852)

Tests results:
failed aytests/sles12.rb
failed aytests/ay_packages.rb
failed aytests/self_update.rb
failed aytests/http.rb
failed aytests/lvm_auto.rb
failed aytests/sles12_all_yast.rb
Build step 'Execute shell' marked build as failure

< Previous Next >
This Thread
Follow Ups