On Sun, Feb 26, 2017 at 3:18 PM, Yaniv Kaul <ykaul@redhat.com> wrote:
On Sun, Feb 26, 2017 at 3:04 PM Shlomo Ben David <sbendavi@redhat.com> wrote:
Hi,
Test failed: [ test-repo_ovirt_experimental_master ]
Link to Job: [1]
Link to all logs: [2]
Link to error log: [3]
[1] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5538
[2] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ master/5538/artifact/exported-artifacts/basic-suit-master- el7/test_logs/basic-suite-master/post-006_migrations.py/
[3] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ master/5538/artifact/exported-artifacts/basic-suit-master- el7/nosetests-006_migrations.py.xml
Error snippet from the log:
The below is not the issue. The issue is (engine log): 2017-02-26 05:43:52,178-05 ERROR [org.ovirt.engine.core.bll.network.host.HostValidator] (default task-11) [d3b3a59d-6cc0-4896-b3f2-8483f9b77fe2] Unable to setup network: operation can only be done when Host status is one of: Maintenance, Up, NonOperational; current status is Connecting
And it comes from the host disconnecting a bit from engine, with various errors such as (again, engine log):
2017-02-26 05:43:26,763-05 ERROR [org.ovirt.engine.core.dal. dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler5) [63e30973] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM lago-basic-suite-master-host1 *command FullListVDS failed: Unrecognized message received*
The error Shlomo posted may not be the error failing the test, but is is very important error that must not be in vdsm logs. Nir