Bug 1200718 - [oVirt] require libvirt-python that properly supports virDomainBlockCopy
Summary: [oVirt] require libvirt-python that properly supports virDomainBlockCopy
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: m1
: 3.6.0
Assignee: Nir Soffer
QA Contact: Ori Gofen
URL:
Whiteboard: storage
Depends On: 1155484 1199682 1209839
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-11 09:35 UTC by Allon Mureinik
Modified: 2016-05-26 01:50 UTC (History)
10 users (show)

Fixed In Version: v4.17.0.4
Clone Of:
Environment:
Last Closed: 2015-11-04 12:59:19 UTC
oVirt Team: Storage
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 39551 0 master MERGED spec: Update libvirt-daemon and libvirt-python requirements Never
oVirt gerrit 40069 0 master MERGED vm: Use blockCopy for live storage migration Never

Description Allon Mureinik 2015-03-11 09:35:37 UTC 
Description of problem:
The virDomainBlockCopy is libvirt is required for several flows which change snapshots, specifically LSM and (live) merge.
Looking forward, we should drop support for libvirt versions that don't provide it, and require ones that do.

For Fedora: libvirt-python-1.2.9-2 (see bug 1199682)
For EL: libvirt-python-1.2.8-5 (see bug 1155484)
Comment 1 Ori Gofen 2015-06-29 12:13:51 UTC 
on rhel the require has been met, on fedora20 the installed package has lower viersion:
"libvirt-python x86_64 1.1.3.9-1.fc20"

Nir please advise
Comment 2 Nir Soffer 2015-06-29 12:33:58 UTC 
(In reply to Ori Gofen from comment #1)
> on rhel the require has been met, on fedora20 the installed package has
> lower viersion:

We do not support fedora 20 any more. Please test with fedora 21.
Comment 3 Ori Gofen 2015-06-30 08:36:49 UTC 
since when???
Verified per comment #2.
Comment 4 Sandro Bonazzola 2015-11-04 12:59:19 UTC 
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.
Note You need to log in before you can comment on or make changes to this bug.