Bug 1431188 – Host unavailable after upgrade from RHEL-H 7.3 (RHEV 3.6) upgrade to RHEL-H 7.3 (RHV 4.0) with a busy RHVM

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1431188 - Host unavailable after upgrade from RHEL-H 7.3 (RHEV 3.6) upgrade to RHEL-H 7.3 (RHV 4.0) with a busy RHVM

Summary:	Host unavailable after upgrade from RHEL-H 7.3 (RHEV 3.6) upgrade to RHEL-H 7...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	vdsm (Show other bugs)
Sub Component:
Version:	3.6.10
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	ovirt-4.2.0
Target Release:	---
Assigned To:	Dan Kenigsberg
QA Contact:	Mor
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	1431228
Blocks:	1445920
	Show dependency tree / graph

Reported:	2017-03-10 09:44 EST by Douglas Schilling Landgraf
Modified:	2018-05-15 13:52 EDT (History)
CC List:	14 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Clones:	1445920 (view as bug list)
Environment:
Last Closed:	2018-05-15 13:50:23 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2018:1489	None	None	None	2018-05-15 13:52 EDT

Groups: None (edit)

Description Douglas Schilling Landgraf 2017-03-10 09:44:53 EST

Description of problem:

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

RHEVM 4.0.6.3-0.1.el7
RHEL-H 7.3 on 3.6


How reproducible:

- Add the repositories in the hypervisor for 4.0 upgrade
- Click Upgrade button in the Engine 
- Hosts will be unavailable, lost network and had to redeploy

Comment 3 Martin Perina 2017-03-10 10:49:36 EST

Douglas, could you please provide both engine and VDSM logs?

Comment 6 Dan Kenigsberg 2017-03-12 04:35:13 EDT

Adrian, Douglas, could you attach sosreport from the host *prior* to the redeployment? This bug should be dedicated to the first failed upgrade. comment  5 analyses another problem with the redeployed host.

Comment 12 Dan Kenigsberg 2017-03-21 08:28:53 EDT

This probably shares an underlying reason with bug 1431228: ActivateVdsCommand takes unbearably long time to finish.

Comment 13 rhev-integ 2017-04-26 06:51:43 EDT

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[FOUND CLONE FLAGS: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ]

For more info please contact: rhv-devops@redhat.com

Comment 16 Michael Burman 2017-11-06 01:13:59 EST

Dan, i think the summary of this bug should be changed as it's a pure performance bug and fully depends on Bug 1431228 - Long time for operations when updating hosts data in RHEVM and has no paatches of it's own..

Comment 17 Michael Burman 2017-11-06 03:36:25 EST

Indeed, all that needs to be done here is to add an NGN to the big setup built for verification of bug 1431228.

Comment 18 Mor 2017-11-30 07:22:30 EST

Verified on:
Red Hat Virtualization Manager version: 4.2.0-0.5.master.el7
Red Hat Virtualization Host 4.2.0 (el7.4)

Comment 19 RHV Bugzilla Automation and Verification Bot 2017-12-06 11:18:28 EST

INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[No external trackers attached]

For more info please contact: rhv-devops@redhat.com

Comment 20 RHV Bugzilla Automation and Verification Bot 2017-12-12 16:16:39 EST

INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[No external trackers attached]

For more info please contact: rhv-devops@redhat.com

Comment 21 RHV Bugzilla Automation and Verification Bot 2017-12-18 12:06:06 EST

INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[No external trackers attached]

For more info please contact: rhv-devops@redhat.com

Comment 27 errata-xmlrpc 2018-05-15 13:50:23 EDT

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-2018:1489

Note You need to log in before you can comment on or make changes to this bug.