Hide Forgot
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", "attachment": { "path": "/dev/sda", "scsi_wwn": "20024f400585401ce", "type": "block" } }
Please provide a clear scenario
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`.
verified on ovirt-engine 4.3.2-0.1.el7 vdsm-4.30.10-1.el7ev.x86_64
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.