Bug 1290844

Summary: [Debian] provide libvirt >= 1.2.17 for vdsm >= 4.17.13
Product: [oVirt] ovirt-distribution Reporter: Sandro Bonazzola <sbonazzo>
Component: GeneralAssignee: Milan Zamazal <mzamazal>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs, didi, lveyde, mzamazal, sbonazzo, stirabos, ylavi
Target Milestone: ---Flags: sbonazzo: ovirt-4.3-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-27 07:28:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: External RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2015-12-11 15:43:43 UTC
Description of problem:
Debian Jessie currently has libvirt 1.2.9.
In order to have memory hotplug working we need a newer version.

Comment 1 Sandro Bonazzola 2016-03-11 08:23:01 UTC
Moving to Milan since he's porting vdsm to Debian

Comment 2 Milan Zamazal 2016-03-11 15:22:19 UTC
The best way to handle this would be to coordinate with Debian Libvirt Maintainers to make an official jessie backport of libvirt.  Let's see whether the overall jessie backport is worth the effort (i.e. whether there's a real demand for that from users) after I finish the Vdsm packaging for unstable.

Comment 3 Yaniv Kaul 2016-05-04 18:05:52 UTC
Moving to 4.0, though I suggest closing if not handled.

Comment 4 Yaniv Lavi 2016-05-23 13:14:03 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 5 Yaniv Kaul 2016-11-21 10:34:10 UTC
Do we want to keep monitoring our Debian support here, or switch to some other (Debian related) bug database?
Are we ever going to handle this, or should I CLOSE-DEFERRED this?

Comment 6 Milan Zamazal 2016-11-21 14:31:01 UTC
I don't think it makes sense tracking Debian packaging here. We have removed Debian packaging from Vdsm since it was completely broken. It's better to track the Debian packaging effort directly in Debian and/or on ovirt-devel mailing list. The intent-to-package bug for Vdsm in Debian is https://bugs.debian.org/668538, this is what we start with. If we manage to make a working Vdsm Debian package, its bugs should be reported to Debian BTS. So I'd suggest closing the Debian packaging bugs in Vdsm Bugzilla.

Comment 7 Milan Zamazal 2018-03-21 16:38:23 UTC
I don't think anybody cares about using Debian hosts anymore and I've abandoned my Debian work for that reason long time ago. So I suggest closing this bug as WONTFIX.