Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1547369

Summary: VDSM: Mark VM.getDiskAlignment as deprecated for 4.2
Product: [oVirt] vdsm Reporter: Allon Mureinik <amureini>
Component: Bindings-APIAssignee: Allon Mureinik <amureini>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.20.0CC: bugs, ebenahar
Target Milestone: ovirt-4.2.2Keywords: CodeChange
Target Release: ---Flags: rule-engine: ovirt-4.2+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:09:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1533086    

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.