Bug 1342559 - Information about LV role(s) not provided
Summary: Information about LV role(s) not provided
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.154
Hardware: All
OS: All
low
low
Target Milestone: Fedora
: 2016-06
Assignee: Tony Asleson
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-03 14:11 UTC by Vratislav Podzimek
Modified: 2017-09-13 15:54 UTC (History)
14 users (show)

Fixed In Version: 2.02.156
Clone Of:
Environment:
Last Closed: 2017-09-13 15:54:21 UTC
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?


Attachments (Terms of Use)

Description Vratislav Podzimek 2016-06-03 14:11:41 UTC
Description of problem:
LVM provides a neat way how to determine the function of an LV - its Role. This can be get e.g. by adding '-o+role' to the 'lvs' command. However, this information is missing in the DBus API (the LVs' DBus objects).

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

How reproducible:
100%

Steps to Reproduce:
1. create an LV
2. try to get its role via the DBus API

Actual results:
information missing

Expected results:
Role provided

Additional info:
since the value from 'lvs -o+role' is a comma-separated list of roles as strings, the best type for a new 'Roles' property of the 'LvCommon' interface seems to be 'as' - array of strings parsed from the comma-separated list.

Comment 2 Vratislav Podzimek 2016-06-13 07:21:38 UTC
(In reply to Tony Asleson from comment #1)
> Committed upstream
> 
> https://git.fedorahosted.org/cgit/lvm2.git/commit/
> ?id=3bf43a65fefbda1b2628fbbc77ad40e3780a8d84


Looks good to me, thanks!

Comment 3 Peter Rajnoha 2016-07-01 06:47:04 UTC
Included in 2.02.156.

commit 3bf43a65fefbda1b2628fbbc77ad40e3780a8d84
Author: Tony Asleson <tasleson>
Date:   Fri Jun 3 17:07:37 2016 -0500

    lvmdbusd: Add roles property to LV common interface


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