Bug 1496848

Summary:	Access to RHV using the oVirt SDK may crash the events worker
Product:	Red Hat CloudForms Management Engine	Reporter:	Juan Hernández <juan.hernandez>
Component:	Providers	Assignee:	Juan Hernández <juan.hernandez>
Status:	CLOSED ERRATA	QA Contact:	Angelina Vasileva <anikifor>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.9.0	CC:	gblomqui, jfrey, jhardy, obarenbo, pkliczew, simaishi
Target Milestone:	GA
Target Release:	5.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	rhev
Fixed In Version:	5.9.0.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-01 13:18:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	Bug
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	RHEVM	Target Upstream Version:
Embargoed:

Description Juan Hernández 2017-09-28 15:45:06 UTC

Description of problem:

When use of the oVirt SDK is enabled the events worker may sporadically crash the worker due to a segmentation violation.

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

CFME 5.9.0 (latest master branch)
SDK 4.1.8 (latest stable release)

How reproducible:

In order to reproduce this the use of the SDK has to be enabled, and the events worker has to send simultaneously two requests to the server. This isn't easy to reproduce, as it depends on timing. But it is easy to reproduce in the SDK itself, see bug 1496846.

Steps to Reproduce:

None.

Actual results:

The events worker crashes due to a segmentation fault.

Expected results:

The events worker shouldn't crash.

Additional info:

This issue should only affect newer versions of CFME, were the SDK is enabled by default and the connections are optimised to use one per worker. But I think that we should update older versions of CFME (5.8 and 5.7) to use the fixed version of the SDK once it is available, just in case.

Comment 2 Juan Hernández 2017-10-16 10:52:43 UTC

The potential crash has been resolved in version 4.1.9 of the SDK. The provider needs now to be updated to use this version of the SDK:

  Require oVirt Ruby SDK 4.1.9 or newer
  https://github.com/ManageIQ/manageiq-providers-ovirt/pull/107

Upstream this will happen automatically, but downstream the RPM for the SDK needs to be updated explicitly. Satoe, can you help us with that?

Comment 3 Satoe Imaishi 2017-10-16 13:02:04 UTC

No problem. Will update the downstream rpm after the PR is merged.

Comment 4 Ilanit Stein 2017-12-13 11:17:47 UTC

Moving to Verified based on bug 1496846 verification.
On CFME latest (5.9.0.12), the oVirt Ruby SDK version is:
rh-ruby23-rubygem-ovirt-engine-sdk4-4.1.13-1.el7cf.x86_64,
and fix was included in SDK 4.1.9.

Comment 7 errata-xmlrpc 2018-03-01 13:18:32 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/RHSA-2018:0380