8:52 a.m.
On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
Failing job is
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
Here's the relevant log in engine-setup:
2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd
plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop',
'ovirt-imageio.service'), executable='None', cwd='None', env=None
2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd
plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop',
'ovirt-imageio.service'), rc=0
2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop',
'ovirt-imageio.service') stdout:
2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop',
'ovirt-imageio.service') stderr:
2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd systemd.state:170
starting service ovirt-imageio
2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd
plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start',
'ovirt-imageio.service'), executable='None', cwd='None', env=None
2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd
plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start',
'ovirt-imageio.service'), rc=1
2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start',
'ovirt-imageio.service') stdout:
2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start',
'ovirt-imageio.service') stderr:
Job for ovirt-imageio.service failed because the control process exited with error code.
See "systemctl status ovirt-imageio.service" and "journalctl -xe" for
details.
2020-04-27 09:25:36,633-0400 DEBUG otopi.context context._executeMethod:145 method
exception
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
line 190, in _closeup_resatrt_service
state=state,
File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in
state
service=name,
RuntimeError: Failed to start service 'ovirt-imageio'
2020-04-27 09:25:36,636-0400 ERROR otopi.context context._executeMethod:154 Failed to
execute stage 'Closing up': Failed to start service 'ovirt-imageio'
Looking at the logs at:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exp...
2020-04-27 09:25:39,887 INFO (MainThread) [server] Starting
(pid=17137, version=2.0.5)
2020-04-27 09:25:39,944 ERROR (MainThread) [server] Server failed
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
line 37, in main
server = Server(cfg)
File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
line 76, in __init__
self.remote_service = services.RemoteService(self.config, self.auth)
File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
line 80, in __init__
self._secure_server()
File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
line 95, in _secure_server
raise errors.TlsConfigurationError(*required_config)
ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls]
section in daemon.conf), but not configured: ca_file = , cert_file = ,
key_file =
This means engine-setup did not create correct configuration file.
Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
I don't see /etc/ovirt-imageio directory, maybe the collections scripts
need update?
This works in real setup, so I guess this is another OST environment issue.
Nir
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>*
<https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>*
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
