Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1146648

Summary: master domain down after upgrade, tracebacks in vdsm.log
Product: Red Hat Enterprise Virtualization Manager Reporter: Petr Beňas <pbenas>
Component: vdsmAssignee: Allon Mureinik <amureini>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acanan, amureini, bazulay, ecohen, gklein, iheim, lpeer, lsurette, pstehlik, scohen, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: v4.16.5-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-16 13:39:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vdsm log
none
engine log
none
update log none

Description Petr Beňas 2014-09-25 16:41:15 UTC 
Created attachment 941196 [details]
vdsm log

Description of problem:
master domain cannot be activated after upgrade from vt3.1 to vt4

Version-Release number of selected component (if applicable):
vdsm-4.16.3-3.el7.beta.x86_64

How reproducible:


Steps to Reproduce:
1. upgrade from vt3.1 to vt4 with el7 host over jsonrpc


Actual results:


Expected results:


Additional info:
Comment 1 Petr Beňas 2014-09-25 16:42:48 UTC 
Created attachment 941197 [details]
engine log
Comment 2 Petr Beňas 2014-09-25 16:43:34 UTC 
Created attachment 941204 [details]
update log
Comment 3 Petr Beňas 2014-09-25 16:53:44 UTC 
seems to be resolved by update to vdsm-4.16.5-2.el7.x86_64
Comment 4 Allon Mureinik 2014-09-29 21:10:53 UTC 
(In reply to Petr Beňas from comment #3)
> seems to be resolved by update to vdsm-4.16.5-2.el7.x86_64
Moving to ON_QA to verify based on that comment.

Also, taking the bug so it has an assignee if it fails QA.
Comment 5 Aharon Canan 2014-09-30 08:22:46 UTC 
Do we support upgrade between builds?
anyway VDSM should be upgraded first no?
Comment 6 Petr Beňas 2014-09-30 08:39:40 UTC 
Definitelly, for example z-stream works this way. 
AFAIK it's not documented, so the user can upgrade either engine or vdsm first.
Comment 7 Allon Mureinik 2014-09-30 20:07:01 UTC 
(In reply to Aharon Canan from comment #5)
> Do we support upgrade between builds?
Only between releases (e.g., alpha->beta, beta->rc, etc.)
Upgrade between "internal" builds is a nicety, but we do not guarantee it.
If this issue only reproduces when upgrade vt3.1->vt4, IIUC, it should be closed as NOTABUG.

> anyway VDSM should be upgraded first no?
No.
You can mix and match engine/VDSM versions.
Comment 8 Elad 2014-10-23 07:59:32 UTC 
Upgraded between vt5 to vt7 and master domain activated normally after vdsmd restart


Upgraded vdsm-4.16.6-1.el7.x86_64 to vdsm-4.16.7.1-1.el7.x86_64.rpm
Used a RHEL7 host