Bug 1547369 - VDSM: Mark VM.getDiskAlignment as deprecated for 4.2
Summary: VDSM: Mark VM.getDiskAlignment as deprecated for 4.2
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Bindings-API
Version: 4.20.0
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ovirt-4.2.2
: ---
Assignee: Allon Mureinik
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks: 1533086
TreeView+ depends on / blocked
 
Reported: 2018-02-21 07:27 UTC by Allon Mureinik
Modified: 2018-03-29 11:09 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-29 11:09:23 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87847 0 master MERGED schema: Deprecate VM.getDiskAlignment 2020-05-18 17:38:55 UTC
oVirt gerrit 88019 0 ovirt-4.2 MERGED schema: Deprecate VM.getDiskAlignment 2020-05-18 17:38:55 UTC

Description Allon Mureinik 2018-02-21 07:27:27 UTC 
Description of problem:
As per bug 1533086, the Scan Alignment feature will be removed in 4.3. Therefore, it should be marked as deprecated in 4.2.

Version-Release number of selected component (if applicable):
4.20.*
Comment 1 Elad 2018-02-22 15:58:28 UTC 
It seems the fix is not in the latest build.

https://gerrit.ovirt.org/gitweb?p=vdsm.git;a=shortlog;h=584522ab56c02e55de304e558a085e134b84f5f9


Commit 584522ab56c02e55de304e558a085e134b84f5f9 is not in v4.20.19

Moving to MODIFIED
Comment 2 Elad 2018-03-04 12:22:02 UTC 
VM getDiskAlignment is deprecated in 4.2:


/usr/lib/python2.7/site-packages/vdsm/rpc/vdsm-api.yml:

VM.getDiskAlignment:
    added: '3.2'
    deprecated: '4.2'
    description: Check alignment of virtual machine disk partitions.
    params:
    -   description: The UUID of the VM
        name: vmID
        type: *UUID


Used:
vdsm-4.20.20-1.el7ev.x86_64
Comment 3 Sandro Bonazzola 2018-03-29 11:09:23 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.