<div dir="ltr">After the following fix had been merged, we still had an issue with vm_run but it had been fixed as well.<div>Master experimental is now working properly.</div><div><br></div><div>Thanks Dan</div><div>Gil</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 27, 2016 at 10:24 AM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Tue, Dec 27, 2016 at 9:59 AM, Eyal Edri <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>> wrote:<br>
><br>
><br>
> On Tue, Dec 27, 2016 at 9:56 AM, Eyal Edri <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>> wrote:<br>
>><br>
>> Any updates?<br>
>> The tests are still failing on vdsmd won't start from Sunday... master<br>
>> repos havn't been refreshed for a few days due to this.<br>
>><br>
>> from host deploy log: [1]<br>
>> basic-suite-master-engine/_<wbr>var_log_ovirt-engine/host-<wbr>deploy/ovirt-host-deploy-<wbr>20161227012930-192.168.201.4-<wbr>14af2bf0.log<br>
>> the job links [2]<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> [1]<br>
>> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/lastCompletedBuild/artifact/exported-artifacts/basic_suite_master.sh-el7/exported-artifacts/test_logs/basic-suite-master/post-002_bootstrap.py/lago-" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>test-repo_ovirt_experimental_<wbr>master/lastCompletedBuild/<wbr>artifact/exported-artifacts/<wbr>basic_suite_master.sh-el7/<wbr>exported-artifacts/test_logs/<wbr>basic-suite-master/post-002_<wbr>bootstrap.py/lago-</a><br>
><br>
><br>
> Now with the full link:<br>
> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/lastCompletedBuild/artifact/exported-artifacts/basic_suite_master.sh-el7/exported-artifacts/test_logs/basic-suite-master/post-002_bootstrap.py/lago-basic-suite-master-engine/_var_log_ovirt-engine/host-deploy/ovirt-host-deploy-20161227012930-192.168.201.4-14af2bf0.log" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>test-repo_ovirt_experimental_<wbr>master/lastCompletedBuild/<wbr>artifact/exported-artifacts/<wbr>basic_suite_master.sh-el7/<wbr>exported-artifacts/test_logs/<wbr>basic-suite-master/post-002_<wbr>bootstrap.py/lago-basic-suite-<wbr>master-engine/_var_log_ovirt-<wbr>engine/host-deploy/ovirt-host-<wbr>deploy-20161227012930-192.168.<wbr>201.4-14af2bf0.log</a><br>
><br>
>><br>
>><br>
>><br>
>><br>
>> 016-12-27 01:29:29 DEBUG otopi.plugins.otopi.services.<wbr>systemd<br>
>> plugin.execute:921 execute-output: ('/bin/systemctl', 'start',<br>
>> 'vdsmd.service') stdout:<br>
>><br>
>> 2016-12-27 01:29:29 DEBUG otopi.plugins.otopi.services.<wbr>systemd<br>
>> plugin.execute:926 execute-output: ('/bin/systemctl', 'start',<br>
>> 'vdsmd.service') stderr:<br>
>> A dependency job for vdsmd.service failed. See 'journalctl -xe' for<br>
>> details.<br>
>><br>
>> 2016-12-27 01:29:29 DEBUG otopi.context context._executeMethod:142 method<br>
>> exception<br>
>> Traceback (most recent call last):<br>
>> File "/tmp/ovirt-QZ1ucxWFfm/<wbr>pythonlib/otopi/context.py", line 132, in<br>
>> _executeMethod<br>
>> method['method']()<br>
>> File<br>
>> "/tmp/ovirt-QZ1ucxWFfm/otopi-<wbr>plugins/ovirt-host-deploy/<wbr>vdsm/packages.py",<br>
>> line 209, in _start<br>
>> self.services.state('vdsmd', True)<br>
>> File "/tmp/ovirt-QZ1ucxWFfm/otopi-<wbr>plugins/otopi/services/<wbr>systemd.py",<br>
>> line 141, in state<br>
>> service=name,<br>
>> RuntimeError: Failed to start service 'vdsmd'<br>
>> 2016-12-27 01:29:29 ERROR otopi.context context._executeMethod:151 Failed<br>
>> to execute stage 'Closing up': Failed to start service 'vdsmd'<br>
>> 2016-12-27 01:29:29 DEBUG otopi.context context.dumpEnvironment:760<br>
>> ENVIRONMENT DUMP - BEGIN<br>
>> 2016-12-27 01:29:29 DEBUG otopi.context context.dumpEnvironment:770 ENV<br>
>> BASE/error=bool:'True'<br>
>> 2016-12-27 01:29:29 DEBUG otopi.context context.dumpEnvironment:770 ENV<br>
>> BASE/excep<br>
>><br>
>> [2]<br>
>> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/lastCompletedBuild/testReport/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>test-repo_ovirt_experimental_<wbr>master/lastCompletedBuild/<wbr>testReport/</a><br>
<br>
<br>
</div></div>In the log I see<br>
<br>
Processing package vdsm-4.20.0-7.gitf851d1b.el7.<wbr>centos.x86_64<br>
<br>
which is from Dec 22 (last Thursday). This is because of us missing a<br>
master-branch tag. v4.20.0 wrongly tagged on the same commit as that<br>
of v4.19.1, removed, and never placed properly.<br>
<br>
I've re-pushed v4.20.0 properly, and now merged a patch to trigger<br>
build-artifacts in master.<br>
<a href="http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/1544/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>vdsm_master_build-artifacts-<wbr>el7-x86_64/1544/</a><br>
<br>
When this is done, could you use it to take the artifacts and try again?<br>
<br>
Regards,<br>
Dan.<br>
</blockquote></div><br></div>