I posted https://gerrit.ovirt.org/#/c/107830/ to improve logging during storage setup.On Fri, Mar 20, 2020 at 9:35 PM Nir Soffer <nsoffer@redhat.com> wrote:
Looks like infrastructure issue setting up storage on engine host.
Here are 2 failing builds with unrelated changes:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6677/
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6678/
Rebuilding still fails in setup_storage:
Is this a known issue?
Error Message
AssertionError: setup_storage.sh failed. Exit code is 1 assert 1 == 0 -1 +0
Stacktrace
prefix = <ovirtlago.prefix.OvirtPrefix object at 0x7f6fd2b998d0>
@pytest.mark.run(order=14)def test_configure_storage(prefix):engine = prefix.virt_env.engine_vm()result = engine.ssh(['/tmp/setup_storage.sh',],)> assert result.code == 0, 'setup_storage.sh failed. Exit code is %s' % result.codeE AssertionError: setup_storage.sh failed. Exit code is 1E assert 1 == 0E -1E +0
The pytest traceback is nice, but in this case it is does not show any useful info.
Since we run a script using ssh, the error message should include the process stdout and stderrwhich probably can explain the failure.
That's true, but the pytest porting effort was about providing a bare minimum to move away from nose.
Also I wonder why this code is called as a test (test_configure_storage). This looks like setupstep so it should run as a fixture.
Nir