Bug 887552

Summary: 3.2 Upgrade: version lock contents are lost after upgrade from 3.0 to 3.1
Product: Red Hat Enterprise Virtualization Manager Reporter: Yaniv Kaul <ykaul>
Component: ovirt-engine-setupAssignee: Moran Goldboim <mgoldboi>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: alourie, bazulay, dyasny, iheim, italkohe, jkt, Rhev-m-bugs, sgrinber, ykaul
Target Milestone: ---Keywords: ZStream
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 888223 (view as bug list) Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 888223    

Description Yaniv Kaul 2012-12-16 10:16:43 UTC 
Description of problem:
On rhevm-3 (QA's production setup) which was upgraded from 3.0.7 to 3.1 (SI24), in several iterations (due to multiple upgrade failures which required rollbacks), there is no version lock contents whatsoever:


[root@rhevm-3 ~]# cat /etc/yum/pluginconf.d/versionlock.conf
[main]
enabled = 1
locklist = /etc/yum/pluginconf.d/versionlock.list
#  Uncomment this to lock out "upgrade via. obsoletes" etc. (slower)
# follow_obsoletes = 1
[root@rhevm-3 ~]# cat /etc/yum/pluginconf.d/versionlock.list
[root@rhevm-3 ~]# ls -l /etc/yum/pluginconf.d/versionlock.list
-rw-r--r--. 1 root root 0 Nov 26 10:22 /etc/yum/pluginconf.d/versionlock.list


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Itamar Heim 2012-12-16 11:47:07 UTC 
didn't see this on another environment.
yaniv - was the upgrade maybe stopped during the phase it installs the new rpms?
moran - shouldn't upgrade fix this list even if it wasn't there in the begining.
Comment 3 Yaniv Kaul 2012-12-18 06:54:44 UTC 
How do we reproduce it? While it happened, I'm not sure it happens all the time.
Comment 4 Moran Goldboim 2012-12-18 07:10:37 UTC 
(In reply to comment #3)
> How do we reproduce it? While it happened, I'm not sure it happens all the
> time.

happens on 3.0->3.1 upgrade, workaround is a following 3.1->3.1.z upgrade.
Comment 5 Yaniv Kaul 2012-12-18 07:36:17 UTC 
(In reply to comment #4)
> (In reply to comment #3)
> > How do we reproduce it? While it happened, I'm not sure it happens all the
> > time.
> 
> happens on 3.0->3.1 upgrade, workaround is a following 3.1->3.1.z upgrade.

I assume via rhevm-upgrade, as there's no versionlock?
Comment 6 Alex Lourie 2012-12-18 07:58:40 UTC 
(In reply to comment #5)
> 
> I assume via rhevm-upgrade, as there's no versionlock?

Yes. The rhevm-upgrade will restore the versionlock list.
Comment 10 Itamar Heim 2013-06-11 08:55:18 UTC 
3.2 has been released
Comment 11 Itamar Heim 2013-06-11 08:55:21 UTC 
3.2 has been released
Comment 12 Itamar Heim 2013-06-11 08:55:31 UTC 
3.2 has been released
Comment 13 Itamar Heim 2013-06-11 08:58:18 UTC 
3.2 has been released
Comment 14 Itamar Heim 2013-06-11 09:27:51 UTC 
3.2 has been released