On Dec 27, 2016 3:01 PM, "Gil Shinar" <gshinar@redhat.com> wrote:

After the following fix had been merged, we still had an issue with vm_run but it had been fixed as well.

Master experimental is now working properly.

Excellent news!   

1. Can we publish it? 

2. 4.1 branch? 

Y. 

Thanks Dan

Gil

On Tue, Dec 27, 2016 at 10:24 AM, Dan Kenigsberg <danken@redhat.com> wrote:

On Tue, Dec 27, 2016 at 9:59 AM, Eyal Edri <eedri@redhat.com> wrote:
>
>
> On Tue, Dec 27, 2016 at 9:56 AM, Eyal Edri <eedri@redhat.com> wrote:
>>
>> Any updates?
>> The tests are still failing on vdsmd won't start from Sunday... master
>> repos havn't been refreshed for a few days due to this.
>>
>> from host deploy log: [1]
>> basic-suite-master-engine/_var_log_ovirt-engine/host-deploy/ovirt-host-deploy-20161227012930-192.168.201.4-14af2bf0.log
>> the job links [2]
>>
>>
>>
>>
>>
>> [1]
>> 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-
>
>
> Now with the full link:
> 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
>
>>
>>
>>
>>
>> 016-12-27 01:29:29 DEBUG otopi.plugins.otopi.services.systemd
>> plugin.execute:921 execute-output: ('/bin/systemctl', 'start',
>> 'vdsmd.service') stdout:
>>
>> 2016-12-27 01:29:29 DEBUG otopi.plugins.otopi.services.systemd
>> plugin.execute:926 execute-output: ('/bin/systemctl', 'start',
>> 'vdsmd.service') stderr:
>> A dependency job for vdsmd.service failed. See 'journalctl -xe' for
>> details.
>>
>> 2016-12-27 01:29:29 DEBUG otopi.context context._executeMethod:142 method
>> exception
>> Traceback (most recent call last):
>>   File "/tmp/ovirt-QZ1ucxWFfm/pythonlib/otopi/context.py", line 132, in
>> _executeMethod
>>     method['method']()
>>   File
>> "/tmp/ovirt-QZ1ucxWFfm/otopi-plugins/ovirt-host-deploy/vdsm/packages.py",
>> line 209, in _start
>>     self.services.state('vdsmd', True)
>>   File "/tmp/ovirt-QZ1ucxWFfm/otopi-plugins/otopi/services/systemd.py",
>> line 141, in state
>>     service=name,
>> RuntimeError: Failed to start service 'vdsmd'
>> 2016-12-27 01:29:29 ERROR otopi.context context._executeMethod:151 Failed
>> to execute stage 'Closing up': Failed to start service 'vdsmd'
>> 2016-12-27 01:29:29 DEBUG otopi.context context.dumpEnvironment:760
>> ENVIRONMENT DUMP - BEGIN
>> 2016-12-27 01:29:29 DEBUG otopi.context context.dumpEnvironment:770 ENV
>> BASE/error=bool:'True'
>> 2016-12-27 01:29:29 DEBUG otopi.context context.dumpEnvironment:770 ENV
>> BASE/excep
>>
>> [2]
>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/lastCompletedBuild/testReport/

In the log I see

Processing package vdsm-4.20.0-7.gitf851d1b.el7.centos.x86_64

which is from Dec 22 (last Thursday). This is because of us missing a
master-branch tag. v4.20.0 wrongly tagged on the same commit as that
of v4.19.1, removed, and never placed properly.

I've re-pushed v4.20.0 properly, and now merged a patch to trigger
build-artifacts in master.
http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/1544/

When this is done, could you use it to take the artifacts and try again?

Regards,
Dan.