Description of problem: We have seen a couple of customers who have upgraded to the latest version of RHV and when they try to configure and use ImageIO they end up with errors like : "Transfer was paused by system. Reason: failed to add image ticket to ovirt-imageio-proxy." Checking the installed versions of the ImageIO rpms reveal that they are NOT updated to the latest versions released with RHV 4.2 The update scripts seems to miss these rpms. Even if customers had not chosen to configure for ImageIO at the time of upgrade, at least during setup, there must be some way ( like supported versions of OS )to prompt them to update to latest available versions .
The described issue seems similar to bug 1427161 and bug 1306212. The upgrade documentation already instructs to run 'yum update' following engine-setup (on section '2.2. Update the Red Hat Virtualization Manager')[1]. So the imageio-proxy rpm should be updated when following this step. @Anitha - To which 'update scripts' are you referring? [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/upgrade_guide/#Updating_the_Red_Hat_Virtualization_Manager_3.6
I see updates to imageio packages when I run "yum update". Can you explain how to reproduce this issue?
Sandro, is there some mechanism in engine setup that need to be updated to make sure imageio packages are updated? We assume that publishing new package in the channels is enough, and engine-setup should do the right thing without any configuration.
(In reply to Nir Soffer from comment #5) > Sandro, is there some mechanism in engine setup that need to be updated to > make > sure imageio packages are updated? > > We assume that publishing new package in the channels is enough, and > engine-setup > should do the right thing without any configuration. a "yum update" is suggested also in the documentation, but if you want engine-setup to take care of updating imageio instead of yum you need to add the packages you need updated to engine setup code. grep sources for DEFAULT_ADDITIONAL_PACKAGES to find where to add the packages you need updated during engine-setup execution. Please note that if you need to update a setup plugin before engine-setup execution you'll need to update the engine spec file for requiring it.
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Hi Anitha, Can you please confirm that the packages are still not being updated after running yum update? It is part of every upgrade flow to run `yum update` after engine-setup: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/upgrade_guide/upgrading_from_4-1 But even if after `yum update` the package is not being update, it is a problem. Otherwise I suggest closing the bug as WORKSFORME. Thanks!
Needinfo pending for 2 months, closing until new information is provided
(In reply to Tal Nisan from comment #11) > Needinfo pending for 2 months, closing until new information is provided Tal, Not sure how I missed this . I verified on an upgraded system that the components do get updated. We are good to go. Thanks.