Bug 1578857

Summary: Host upgrade from rhvh-4.1-0.20180410.0 to rhvh-4.2.3.0-0.20180508.0 fails
Product: Red Hat Enterprise Virtualization Manager Reporter: Koutuk Shukla <kshukla>
Component: imgbasedAssignee: Ryan Barry <rbarry>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.11CC: dfediuck
Target Milestone: ---Flags: lsvaty: testing_plan_complete-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-16 14:06:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Koutuk Shukla 2018-05-16 13:49:20 UTC 
Description of problem:
Host upgrade from rhvh-4.1-0.20180410.0 to rhvh-4.2.3.0-0.20180508.0 fails

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

rhevm: Red Hat Virtualization Manager Version: 4.1.11.2-0.1.el7 

Hypervisor
OS Version:RHEL - 7.5-0.14 - 10.5.el7
OS Description: Red Hat Virtualization Host 4.1 (el7.5-0.14)
Kernel Version:3.10.0 - 862.el7.x86_64
VDSM Version:vdsm-4.19.50-1.el7ev


How reproducible:
100%


Steps to Reproduce:
1. Perform upgrade from rhvh-4.1-0.20180410.0 to rhvh-4.2.3.0-0.20180508.0
2.
3.

Actual results:
Upgrade fails

Expected results:
Upgrade should succeed.

Additional info:
Comment 2 Ryan Barry 2018-05-16 14:06:50 UTC 
Can you please post all of imgbased.log?

This strongly appears to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1573334

In the meantime, can the customer please remove the LVs from the failed upgrade to 4.1.11 and try upgrading again?

lvremove /dev/rhvh/rhvh-4.2.3.0-0.20180508.0+1
lvremove /dev/rhvh/rhvh-4.2.3.0-0.20180508.0
lvremove /dev/rhvh/rhvh-rhvh-4.1-0.20180425.0+1
lvremove /dev/rhvh/rhvh-rhvh-4.1-0.20180425.0

*** This bug has been marked as a duplicate of bug 1573334 ***
Comment 6 Franta Kust 2019-05-16 13:04:30 UTC 
BZ<2>Jira Resync