Bug 2072100

Summary:	vdsmd 4.4.0 throws an exception in asyncore.py while updating OVF data
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	amashah
Component:	vdsm	Assignee:	Marcin Sobczyk <msobczyk>
Status:	CLOSED ERRATA	QA Contact:	Shir Fishbain <sfishbai>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3.22	CC:	abawer, aefrat, alexandermurashkin, bugs, emarcus, gveitmic, izuckerm, jfindysz, lsurette, lsvaty, michal.skrivanek, mkalinin, mperina, msobczyk, nsoffer, pelauter, sfishbai, srevivo, tnisan, ycui
Target Milestone:	ovirt-4.3.23	Keywords:	ZStream
Target Release:	4.3.23
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	vdsm-4.30.53	Doc Type:	Release Note
Doc Text:	A fix for BZ1785061 has been backported to vdsm-4.30.53	Story Points:	---
Clone Of:	1785061	Environment:
Last Closed:	2022-06-30 07:32:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1785061
Bug Blocks:

Description amashah 2022-04-05 15:26:29 UTC

+++ This bug was initially created as a clone of Bug #1785061 +++

Description of problem:

vdsmd throws an exception in asyncore.py while updating OVF data. it happens every hour. During this time the host becomes non responsive, it is soft fenced, and the SPM changes every hour.


Version-Release number of selected component (if applicable):
vdsm-4.30.52-1.el7ev.x86_64




This is a clone of BZ 1785061, where the fix was made for RHV 4.4 only [1], this is a request to backport the fix to vdsm 4.30 as customers have support for 4.3 hosts with EUS with a 4.4 manager.

[1] https://gerrit.ovirt.org/105860

Comment 11 Shir Fishbain 2022-04-12 21:45:09 UTC

Verified

The hotfix build was provided and the verification completed with the following versions:

Engine:ovirt-engine-4.4.10.7-0.4.el8ev.noarch
Vdsm:vdsm-4.30.53-1.el7ev.x86_64

Comment 18 errata-xmlrpc 2022-06-30 07:32:02 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 (vdsm bug fix and enhancement update), 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/RHBA-2022:5440

Comment 19 Shir Fishbain 2022-08-20 21:50:13 UTC

The scenario of this bug already exists in our automation (TestCase6247 in tier2). We will continue to run it during the maintenance period