Bug 1679397

Summary:	RHV upgrade from 4.2.8 to 4.3 fails in RHHI-V environment
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	bipin <bshetty>
Component:	rhhi	Assignee:	Gobinda Das <godas>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhhiv-1.6	CC:	godas, pasik, rcyriac, rhs-bugs, sankarshan, sasundar
Target Milestone:	---
Target Release:	RHHI-V 1.6
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1679399 (view as bug list)		Environment:
Last Closed:	2019-05-09 06:09:09 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:
Embargoed:
Bug Depends On:	1679399
Bug Blocks:	1672932

Description bipin 2019-02-21 05:03:56 UTC

Description of problem:
=======================
While upgrading from RHV-4.2 to RHV-4.3, the upgrade fails in RHHI-V enviornment. Also could see the filesystem under /var/* getting unmounted during the process and never gets mounted back unless me manually remount.


Version-Release number of selected component (if applicable):
============================================================
Upgrade path from rhv 4.2.8.3-0 to rhv 4.3.0.4-0.1


How reproducible:
================
Everytime


Steps to Reproduce:
==================
1.Install rhvh-4.2.8.3-0 on the RHHI-V hypervisors 
2.Upgrade to the rhv 4.3 redhat-virtualization-host image in the UI
3.Fails to upgrade

Actual results:
==============
The upgrade fails 


Expected results:
================
Should successfully complete


Additional info:
===============
COuld see the issue multiple times.

Comment 3 SATHEESARAN 2019-03-29 18:39:40 UTC

Tested upgrade from RHV 4.2.8 to RHV 4.3 (rhvh-4.3.0.5-0.20190328.0+1)

No issues observed, but the VDO errors while stopping the VDO service is noticed,
but that doesn't stopped the upgrade.

Comment 5 errata-xmlrpc 2019-05-09 06:09:09 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:1121