Description of problem: device-mapper-multipath-0.4.9-68.fc21 solves a segfault in multipath. oVirt should consume it on Fedora. There are three possibilities here: 1. Introduce another condition in the spec file to separate f20 and f21 requirements for VDSM - not recommended. 2. Work with multipath maintainers to have the fix backported to f20 - good solution for VDSM, but not sure it's worth the effort on their side. 3. Wait till we no longer need to support f20.
(In reply to Allon Mureinik from comment #0) > 2. Work with multipath maintainers to have the fix backported to f20 - good > solution for VDSM, but not sure it's worth the effort on their side. Let device-mapper-multipath decide that, by cloning the relevant bug to f20 for their inspection, and make it block this bug.
Allon, can you please provide steps to verify this one?
Fedora's Platform QE should verify that this build of device-mapper-multipath indeed solved the aforementioned segfault. oVirt QE's side is to check that VDSM indeed requires a device-mapper-multipath version that includes the fix: rpm -qR vdsm | grep device-mapper-multipath Ala - the spec file seems to require device-mapper-multipath >= 0.4.9-56, not device-mapper-multipath >= 0.4.9-68. Is this intentional? What am I missing here?
Allon, just finished a clean hypervisor re-provision to vdsm 3.6 the spec file gives -> [root@adder ~]# rpm -qR vdsm | grep device-mapper-multipath device-mapper-multipath >= 0.4.9-68 I'm verifying this based on this results
(In reply to Allon Mureinik from comment #3) > Fedora's Platform QE should verify that this build of > device-mapper-multipath indeed solved the aforementioned segfault. > > oVirt QE's side is to check that VDSM indeed requires a > device-mapper-multipath version that includes the fix: > > rpm -qR vdsm | grep device-mapper-multipath > > > Ala - the spec file seems to require device-mapper-multipath >= 0.4.9-56, > not device-mapper-multipath >= 0.4.9-68. Is this intentional? What am I > missing here? Yes, this is intentional. Ben Marzinski provided me that version for Fedora 20.
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.