Bug 1001062

Summary: [rhevm-setup][upgrade] Setup will not be able to roll-back new packages even though the old repo appears on the yum.repos.d
Product: [oVirt] otopi Reporter: Tareq Alayan <talayan>
Component: Plugins.packagersAssignee: Alon Bar-Lev <alonbl>
Status: CLOSED NOTABUG QA Contact: Ilanit Stein <istein>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: acathrow, alonbl, bazulay, dougsland, iheim, Rhev-m-bugs, talayan, yeylon
Target Milestone: ---Flags: talayan: devel_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-26 13:11:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
upgrade log none

Description Tareq Alayan 2013-08-26 12:29:02 UTC 
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:
Comment 1 Tareq Alayan 2013-08-26 12:30:53 UTC 
Created attachment 790487 [details]
upgrade log
Comment 2 Alon Bar-Lev 2013-08-26 12:38:37 UTC 
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!
Comment 3 Tareq Alayan 2013-08-26 13:01:30 UTC 
after updating otopi to otopi.noarch 0:1.1.0-0.8.master.el6ev 

it works successfully.

closing the bz.
Comment 4 Tareq Alayan 2013-08-26 13:04:03 UTC 
before closing the bz. 
I have a question: is it possible force updating the otopi when attemptin to yum update the rhevm-setup?
Comment 5 Alon Bar-Lev 2013-08-26 13:06:56 UTC 
(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.