Bug 1463722

Summary: Failed to start service 'ovirt-imageio-proxy'
Product: [oVirt] ovirt-imageio Reporter: Petr Matyáš <pmatyas>
Component: ProxyAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: amureini, bugs, lsvaty, pmatyas, tnisan, ylavi
Target Milestone: ovirt-4.2.0Keywords: Regression
Target Release: 1.1.0Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
lsvaty: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:15:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/*
none
journal logs none

Description Petr Matyáš 2017-06-21 15:02:09 UTC
Created attachment 1290138 [details]
/var/log/*

Description of problem:
After upgrade from 4.1 to 4.2 service ovirt-imageio-proxy can't be started.

Version-Release number of selected component (if applicable):
ovirt-imageio-proxy-1.0.0-0.201706181640.gita7553fb.el7.centos.noarch

How reproducible:
always

Steps to Reproduce:
1. install 4.1
2. upgrade to 4.2
3.

Actual results:
failed to start ovirt-imageio-proxy

Expected results:
imageio proxy is started correctly

Additional info:

Comment 1 Daniel Erez 2017-06-21 16:18:20 UTC
@Petr, which error are you getting when starting the service? (there's no error in the proxy log)

Comment 2 Red Hat Bugzilla Rules Engine 2017-06-22 06:56:05 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Petr Matyáš 2017-06-22 07:31:27 UTC
Yes exactly, there is no error, the service is just not started, ever.
This doesn't seem to affect anything, just after every engine setup there is error when starting this service.

Comment 4 Daniel Erez 2017-06-22 07:38:33 UTC
(In reply to Petr Matyáš from comment #3)
> Yes exactly, there is no error, the service is just not started, ever.
> This doesn't seem to affect anything, just after every engine setup there is
> error when starting this service.

Can you please attach the output of "systemctl status ovirt-imageio-proxy.service" and "journalctl -xe"

Comment 5 Petr Matyáš 2017-06-22 07:58:34 UTC
Created attachment 1290550 [details]
journal logs

Comment 6 Daniel Erez 2017-06-22 08:12:21 UTC
According to the log [1], there's a missing module in ovirt-imageio-common, that's probably means that the common package wasn't updated. Please try to update 'ovirt-imageio-common' package before executing engine-setup.
(there should be a note about that in the docs - bug 1420602)

[1] Jun 22 07:42:30 localhost.localdomain ovirt-imageio-proxy[684]: Traceback (most recent call last):
Jun 22 07:42:30 localhost.localdomain ovirt-imageio-proxy[684]: File "/usr/bin/ovirt-imageio-proxy", line 26, in <module>
Jun 22 07:42:30 localhost.localdomain ovirt-imageio-proxy[684]: from ovirt_imageio_proxy import image_proxy
Jun 22 07:42:30 localhost.localdomain ovirt-imageio-proxy[684]: File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/image_proxy.py", line 9, in <module>
Jun 22 07:42:30 localhost.localdomain ovirt-imageio-proxy[684]: import server
Jun 22 07:42:30 localhost.localdomain ovirt-imageio-proxy[684]: File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/server.py", line 28, in <module>
Jun 22 07:42:30 localhost.localdomain ovirt-imageio-proxy[684]: from ovirt_imageio_common import ssl
Jun 22 07:42:30 localhost.localdomain ovirt-imageio-proxy[684]: ImportError: cannot import name ssl
Jun 22 07:42:30 localhost.localdomain systemd[1]: ovirt-imageio-proxy.service: main process exited, code=exited, status=1/FAILURE
Jun 22 07:42:30 localhost.localdomain systemd[1]: Failed to start oVirt ImageIO Proxy.
-- Subject: Unit ovirt-imageio-proxy.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit ovirt-imageio-proxy.service has failed.

Comment 7 Petr Matyáš 2017-06-22 08:25:23 UTC
For yum, the "newer" package ovirt-imageio-common-1.0.0-0.201706181639.gita7553fb.el7.centos.noarch.rpm is not an update, since I have ovirt-imageio-common-1.0.0-1.el7.noarch from 4.1 repo.
This has to be the reason for this issue since downgrading ovirt-imageio-common solves the issue.

Comment 8 Petr Matyáš 2017-09-04 14:27:36 UTC
Updated from ovirt-engine-4.1.5.2-1.el7.centos.noarch to ovirt-engine-4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos.noarch
Packages have correct versions now so imageio-proxy works.

Comment 9 Sandro Bonazzola 2017-12-20 11:15:12 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.