Bug 1512481 – "no libgfapi.so.0" found while executing "engine-iso-uploader"

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

Bug 1512481 - "no libgfapi.so.0" found while executing "engine-iso-uploader"

Summary:	"no libgfapi.so.0" found while executing "engine-iso-uploader"

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-iso-uploader (Show other bugs)
Sub Component:
Version:	4.2.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	ovirt-4.2.0
Target Release:	---
Assigned To:	Sandro Bonazzola
QA Contact:	David Necpal
Docs Contact:

URL:
Whiteboard:
Keywords:	EasyFix, Regression

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-11-13 05:27 EST by yisong
Modified:	2018-05-15 13:35 EDT (History)
CC List:	14 users (show)

See Also:
Fixed In Version:	ovirt-iso-uploader-4.1.0-0.2.master.git64c591e.el7ev
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-05-15 13:35:06 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Integration
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:1479	None	None	None	2018-05-15 13:35 EDT

Groups: None (edit)

Comment 1 Michal Skrivanek 2017-11-14 01:00:28 EST

Do we still support engine-iso-uploader?

Comment 4 Sandro Bonazzola 2017-11-20 04:26:36 EST

This is a downstream only issue, upstream package is correct.
Downstream spec file missed a dependency on glusterfs-api

Comment 11 errata-xmlrpc 2018-05-15 13:35:06 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:1479

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