Bug 1346724 – cannot pool-define/create mpath pool

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

Bug 1346724 - cannot pool-define/create mpath pool

Summary:	cannot pool-define/create mpath pool

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	libvirt (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	x86_64 Linux

Priority	high Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Ján Tomko
QA Contact:	Virtualization Bugs
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-06-15 04:53 EDT by yisun
Modified:	2016-11-03 14:47 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	libvirt-2.0.0-1.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Clones:	1347486 (view as bug list)
Environment:
Last Closed:	2016-11-03 14:47:10 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	RHSA-2016:2577	normal	SHIPPED_LIVE	Moderate: libvirt security, bug fix, and enhancement update	2016-11-03 08:07:06 EDT

Groups: None (edit)

Description yisun 2016-06-15 04:53:38 EDT

Description:
cannot pool-define/create mpath pool

versions:
libvirt-1.3.5-1.el7.x86_64

reproduce rate:
100%

THIS IS A REGRESSION BUG, and it works on libvirt-1.3.4-1.el7.x86_64


Steps:
1. # cat pool.mpath
<pool type="mpath">
<name>mpath-pool-1</name>
<target>
<path>/dev/mapper</path>
</target>
</pool>


2. # virsh pool-define pool.mpath
error: Failed to define pool from pool.mpath
error: internal error: missing backend for pool type 7 (mpath)

Actual result:
mpath pool cannot be defined


Expected result:
mpath pool can be defined


Additional info:
This works fined with libvirt-1.3.4-1.el7.x86_64

Comment 2 Ján Tomko 2016-06-17 06:21:54 EDT

Upstream patch:
https://www.redhat.com/archives/libvir-list/2016-June/msg01147.html

Comment 3 Ján Tomko 2016-06-17 09:40:01 EDT

Fixed upstream by:
commit 7303e7079ccfec1bf7d2891c6e87a8646355f124
Author:     Ján Tomko <jtomko@redhat.com>
CommitDate: 2016-06-17 15:35:46 +0200

    configure: define preprocessor macros for SCSI and MPATH
    
    This fixes building these backends when explicitly enabled
    on the command line.
    
    Exposed by commit a659559 which started adding
    --with-storage-mpath in the spec file.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1346724

git describe: v1.3.5-306-g7303e70

Comment 5 yisun 2016-07-26 04:39:56 EDT

Verified on libvirt-2.0.0-3.el7.x86_64 and PASSED

steps:
1. # cat pool.xml 
<pool type="mpath">
<name>mpool</name>
<target>
<path>/dev/mapper</path>
</target>
</pool>


2. # virsh pool-define pool.xml 
Pool mpool defined from pool.xml

3. # virsh pool-undefine mpool
Pool mpool has been undefined

4. # virsh pool-create pool.xml 
Pool mpool created from pool.xml

5. # virsh vol-list mpool
 Name                 Path                                    
------------------------------------------------------------------------------
 dm-2                 /dev/mapper/mpatha                      
 dm-3                 /dev/mapper/mpathb                      
 dm-4                 /dev/mapper/mpathd                      
 dm-5                 /dev/mapper/mpathc                      
 dm-7                 /dev/mapper/mpathg       

6. # virsh pool-dumpxml mpool
<pool type='mpath'>
  <name>mpool</name>
  <uuid>4cb87b5a-4eb5-4e1c-9bb3-1977002ac1c6</uuid>
  <capacity unit='bytes'>96636764160</capacity>
  <allocation unit='bytes'>96636764160</allocation>
  <available unit='bytes'>0</available>
  <source>
  </source>
  <target>
    <path>/dev/mapper</path>
  </target>
</pool>

Comment 7 errata-xmlrpc 2016-11-03 14:47:10 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://rhn.redhat.com/errata/RHSA-2016-2577.html

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