Bug 1472265 – Rebase libvirt-python to current upstream release

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

Bug 1472265 - Rebase libvirt-python to current upstream release

Summary:	Rebase libvirt-python to current upstream release

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	libvirt-python (Show other bugs)
Sub Component:
Version:	7.5
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Jiri Denemark
QA Contact:	weizhang
Docs Contact:

URL:
Whiteboard:
Keywords:	Rebase

Depends On:	1472263 1472268
Blocks:	1469590
	Show dependency tree / graph

Reported:	2017-07-18 06:26 EDT by Jaroslav Suchanek
Modified:	2018-04-10 07:08 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	libvirt-python-3.9.0-1.el7
Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points:	---
Clone Of:	1472263
Environment:
Last Closed:	2018-04-10 07:07:31 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
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:0707	None	None	None	2018-04-10 07:08 EDT

Groups: None (edit)

Description Jaroslav Suchanek 2017-07-18 06:26:48 EDT

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

Both RHEV and OpenStack will like to use new features and APIs provided by libvirt, which are impossible to deliver without rebasing libvirt (there are specific BZs for each of them).

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

libvirt-python >= 3.0.0 (the exact version depends on rebase deadlines)

Comment 5 errata-xmlrpc 2018-04-10 07:07:31 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:0707

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