Bug 1348654

Summary: After installing ovirt-imageio-proxy, engine-setup fails
Product: Red Hat Enterprise Virtualization Manager Reporter: Natalie Gavrielov <ngavrilo>
Component: ovirt-imageio-proxyAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Kevin Alon Goldblatt <kgoldbla>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: aaviram, acanan, alsilva, amureini, derez, gianluca.cecchi, gklein, lsurette, ngavrilo, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.0.1   
Target Release: ---   
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: 2016-08-25 12:44:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Natalie Gavrielov 2016-06-21 16:32:00 UTC
Description of problem:

After installing ovirt-imageio-proxy, engine-setup fails

Version-Release number of selected component:
rhevm-4.0.0.5-0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install engine: yum install rhevm.
2. Perform setup: engine-setup.
3. Install ovirt-imageio-proxy.
4. Run setup again.

Actual results:
[ INFO  ] Upgrading CA
[ ERROR ] Failed to execute stage 'Misc configuration': global name '_get_configuration' is not defined
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160621173820-pibsg7.log
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160621174710-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed


Expected results:
For the setup to pass.

Additional info: editing the script solves this.

Comment 1 Allon Mureinik 2016-06-22 08:26:24 UTC
Please attach the logs.

(In reply to Natalie Gavrielov from comment #0)
> Additional info: editing the script solves this.
What script? How was it edited?

Comment 2 Yaniv Kaul 2016-06-22 08:30:48 UTC
Gil, the scenario described (and it's not very well described) cannot be a blocker in any way.

Comment 3 Amit Aviram 2016-06-22 08:33:15 UTC
This is solved in the current version.

Comment 4 Allon Mureinik 2016-06-22 08:38:23 UTC
Amit, this patch is included in the master branch. Should it be cherry-picked anywhere, or are you planning to do a new tag/release based on master?

Comment 5 Amit Aviram 2016-06-22 08:40:44 UTC
2nd option.

Comment 7 Yaniv Lavi 2016-07-21 12:18:03 UTC
Should this be ON_QA?

Comment 8 Amit Aviram 2016-07-24 08:40:11 UTC
Sandro, this fix is already built for previous versions (it is in ovirt-imageio-proxy-0.3.0...) which is available in ovirt and rhev recent repos. is there anything we further we need to do?

Comment 9 Kevin Alon Goldblatt 2016-08-07 13:36:16 UTC
Verified with the following code:
-----------------------------------
rhevm-4.0.2.4-0.1.el7ev.noarch
vdsm-4.18.10-1.el7ev.x86_64

Verified with the following scenario:
-----------------------------------
1. Updated repos to the code above
2. Run yum update
3. Run engine-setup >>>> Engine-setup is successfull and the ovirt-imageio-proxy was installed as part of the setup

Moving to VERIFIED!

Comment 10 Gianluca Cecchi 2016-08-11 14:08:01 UTC
Hello,
should engine-setup take care also to configure the ovirt-imageio-proxy service or not?

In my case, upgrading from 4.0 to 4.0.2 RC4, the package was installed but the service was neither started nor enabled
 
[root@ractorshe log]# systemctl status ovirt-imageio-proxy.service
● ovirt-imageio-proxy.service - oVirt ImageIO Proxy
   Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
[root@ractorshe log]#

Should this be a manual step taken by a sysadmin?
Tried the upload of an image it fails (goes into pause right after starting).. is this caused byt the service being stopped?

Comment 11 Amit Aviram 2016-08-14 14:33:07 UTC
(In reply to Gianluca Cecchi from comment #10)
> Hello,
> should engine-setup take care also to configure the ovirt-imageio-proxy
> service or not?
> 
> In my case, upgrading from 4.0 to 4.0.2 RC4, the package was installed but
> the service was neither started nor enabled
>  
> [root@ractorshe log]# systemctl status ovirt-imageio-proxy.service
> ● ovirt-imageio-proxy.service - oVirt ImageIO Proxy
>    Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service;
> disabled; vendor preset: disabled)
>    Active: inactive (dead)
> [root@ractorshe log]#
> 
> Should this be a manual step taken by a sysadmin?
> Tried the upload of an image it fails (goes into pause right after
> starting).. is this caused byt the service being stopped?

Yes, the service must be running in order to upload.
Basically engine setup configures ovirt-imageio-proxy, but we have 2 bugs that  needs to be fixed in order for it to work as should: Bug 1365744 ,  Bug 1365451.

Comment 12 Allon Mureinik 2016-08-25 12:44:09 UTC
The fix for this issue was included in RHV 4.