[ OST Failure Report ] [ oVirt 4.1 ] [ 3/4/2017 ] [test_initialize_engine]

Jakub Niedermertl jniederm at redhat.com
Mon Apr 3 16:48:58 UTC 2017


It looks like handling of units 'M' is missing in method mem.py javaX_mb.

On Mon, Apr 3, 2017 at 5:52 PM, Barak Korren <bkorren at redhat.com> wrote:
> Test failed: test_initialize_engine
>
> Link to suspected patches:
> https://gerrit.ovirt.org/75054
>
> Link to Job:
> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1162/
>
> Link to all logs:
> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1162/artifact/exported-artifacts/basic-suit-4.1-el7/test_logs/basic-suite-4.1/post-001_initialize_engine.py/lago-basic-suite-4-1-engine/
>
>
> Error snippet from log:
>
> <error>
>
> 2017-04-03 10:16:48 DEBUG otopi.plugins.otopi.services.systemd
> plugin.execute:926 execute-output: ('/bin/systemctl', 'start',
> 'ovirt-engine.service') stderr:
> Job for ovirt-engine.service failed because the control process exited
> with error code. See "systemctl status ovirt-engine.service" and
> "journalctl -xe" for details.
>
> 2017-04-03 10:16:48 DEBUG otopi.context context._executeMethod:142
> method exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132,
> in _executeMethod
>     method['method']()
>   File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py",
> line 57, in _closeup
>     state=True,
>   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in state
>     service=name,
> RuntimeError: Failed to start service 'ovirt-engine'
>
>
> </error>
>
>
>
> --
> Barak Korren
> bkorren at redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra


More information about the Infra mailing list