Hide Forgot
Description of problem: Setup will not be able to rollback new packages in case of a failure, because installed ones were not found in enabled repositories. Version-Release number of selected component (if applicable): is11 How reproducible: always Steps to Reproduce: 1. is10 installed and running 2. modify rhevm.repo file to have is11 instaed of is10 3. yum update rhevm-setup 4. rhevm-setup 5. Setup will not be able to rollback new packages in case of a failure, because installed ones were not found in enabled repositories. Which is ok since the old repo is not found in the repo file. 6. add the old repo 7. run rhevm-setup again 8. same message as step 5 Actual results: Setup will not be able to rollback new packages in case of a failure, because installed ones were not found in enabled repositories. Expected results: the message won't appear since the old repo is there and enabled Additional info:
Created attachment 790487 [details] upgrade log
Can you please make sure you have the latest otopi at channel installed? This sequence was verified at bug#998921 and found to be working. Thanks!
after updating otopi to otopi.noarch 0:1.1.0-0.8.master.el6ev it works successfully. closing the bz.
before closing the bz. I have a question: is it possible force updating the otopi when attemptin to yum update the rhevm-setup?
(In reply to Tareq Alayan from comment #4) > before closing the bz. > I have a question: is it possible force updating the otopi when attemptin to > yum update the rhevm-setup? yes. however I chose not to do so. ovirt-engine-3.3.0 requires >=otopi-1.1.0 which is forced update over ovirt-engine-3.2.z, so for customers will get the correct package version. for the rollback issue which is mid releases I did not want to add noise to 3.3 spec pre-release. but soon I will release otopi-1.1.0 and then I will force released package for ovirt-engine.