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.
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?
Gil, the scenario described (and it's not very well described) cannot be a blocker in any way.
This is solved in the current version.
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?
2nd option.
Should this be ON_QA?
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?
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!
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?
(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.
The fix for this issue was included in RHV 4.