Bug 1668727 - Cinderlib- implement ManagedVolume.volume_info
Summary: Cinderlib- implement ManagedVolume.volume_info
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: 4.30.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.3.1
: ---
Assignee: Vojtech Juranek
QA Contact: Avihai
Depends On:
Blocks: 1539837
TreeView+ depends on / blocked
Reported: 2019-01-23 13:01 UTC by Fred Rolland
Modified: 2019-03-13 16:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-03-13 16:40:31 UTC
oVirt Team: Storage
aefrat: needinfo-
aefrat: needinfo-
aefrat: needinfo-
rule-engine: ovirt-4.3+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 97186 0 master MERGED storage: add volumes_info 2019-02-11 15:27:18 UTC

Description Fred Rolland 2019-01-23 13:01:43 UTC
Description of problem:

Implement ManagedVolume.volume_info:

Get volume information

The user is able to get the information of a specific volume using
ManagedVolume.volume_info with the volume ID.
Vdsm will return the volume information, as in the attach flow.
For example:

  "path" : "/dev/mapper/20024f400585401ce",
    "path": "/dev/sda",
    "scsi_wwn": "20024f400585401ce",
    "type": "block"

Comment 1 Shir Fishbain 2019-03-07 16:18:51 UTC
Please provide a clear scenario

Comment 4 Vojtech Juranek 2019-03-11 10:38:50 UTC
Tests scenario:
1. Add couple of records into sqlite database /var/lib/vdsm/storage/managedvolume.db
   The records can look like this:
        "connection_info": {
            "connection": 1
        "path": "/dev/mapper/36001405376e34ea70384de7a34a2854d", 
        "vol_id": "vol-id-1", 
        "attachment": {
            "path": "/dev/sda",
            "scsi_wwn": "20024f400585401ce",
            "type": "block"
        "exists": false

2. Run 
     vdsm-client ManagedVolume volumes_info
   and verify it returns all the records.

3. Create json file `ids.json` with IDs of records which are subset of all insrted records, e.g.
       "vol_ids": ["vol-id-1", "vol-id-3"]

4. Run 
     vdsm-client -f ids.json ManagedVolume volumes_info
   and verify it returns only the records which ID's are in `ids.json`.

Comment 5 Avihai 2019-03-11 11:39:26 UTC
verified on ovirt-engine 4.3.2-0.1.el7

Comment 6 Sandro Bonazzola 2019-03-13 16:40:31 UTC
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

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