Anton, looks like vdsmd again failed to load, please try to check if it's related to latest changes.

from host-deploy logs:

017-08-21 06:02:37,616-0400 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.packages plugin.execute:926 execute-output: ('/bin/vdsm-tool', 'configure', '--force') stderr:
Error:  ServiceNotExistError: Tried all alternatives but failed:
ServiceNotExistError: dev-hugepages1G.mount is not native systemctl service
ServiceNotExistError: dev-hugepages1G.mount is not a SysV service 


2017-08-21 06:02:43,407-0400 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/bin/systemctl', 'start', 'vdsmd.service') stderr:
Job for vdsmd.service failed because the control process exited with error code. See "systemctl status vdsmd.service" and "journalctl -xe" for details.

2017-08-21 06:02:43,407-0400 DEBUG otopi.context context._executeMethod:142 method exception
Traceback (most recent call last):
  File "/tmp/ovirt-5Wr0n5bqhG/pythonlib/otopi/context.py", line 132, in _executeMethod
    method['method']()
  File "/tmp/ovirt-5Wr0n5bqhG/otopi-plugins/ovirt-host-deploy/vdsm/packages.py", line 224, in _start
    self.services.state('vdsmd', True)
  File "/tmp/ovirt-5Wr0n5bqhG/otopi-plugins/otopi/services/systemd.py", line 141, in state
    service=name,
RuntimeError: Failed to start service 'vdsmd'
2017-08-21 06:02:43,410-0400 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Failed to start service 'vdsmd'
2017-08-21 06:02:43,411-0400 DEBUG otopi.context context.dumpEnvironment:761 ENVIRONMENT DUMP - BEGIN
2017-08-21 06:02:43,412-0400 DEBUG otopi.context context.dumpEnvironment:771 ENV BASE/error=bool:'True'
2017-08-21 06:02:43,412-0400 DEBUG otopi.context context.dumpEnvironment:771 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError("Failed to start service 'vdsmd'",), <traceback object at 0x3928c20>)]'
2017-08-21 06:02:43,413-0400 DEBUG otopi.context context.dumpEnvironment:775 ENVIRONMENT DUMP - END


On Mon, Aug 21, 2017 at 1:08 PM, oVirt Jenkins <jenkins@ovirt.org> wrote:
A system test invoked by the "ovirt-master" change queue including change
80213,3 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 80749,3 (vdsm) that this change depends on or is based on,
was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 80749,3 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/80213/3

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/80749/3

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1873/
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra



--

Eyal edri


ASSOCIATE MANAGER

RHV DevOps

EMEA VIRTUALIZATION R&D


Red Hat EMEA

TRIED. TESTED. TRUSTED.
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)