Bug 1618433

Summary: REST API reports wrong address and path for NFS storage domain on IPv6
Product: [oVirt] ovirt-engine Reporter: Dominik Holler <dholler>
Component: RestAPIAssignee: shani <sleviim>
Status: CLOSED CURRENTRELEASE QA Contact: shani <sleviim>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.5CC: bugs, danken, ebenahar, frolland, lveyde, tnisan
Target Milestone: ovirt-4.2.7Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.7.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-02 14:36:34 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: 1080725, 1618676    

Description Dominik Holler 2018-08-16 16:01:54 UTC
Description of problem:
REST API reports wrong address and path for NFS storage domain on IPv6




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


How reproducible:


Steps to Reproduce:
1. Create NFS storage domain on IPv6
2. GET storage domain on REST API, e.g. by http://fedora-28-gui:8080/ovirt-engine/api/storagedomains/abc

Actual results:
<storage_domains>
    <storage_domain href="/ovirt-engine/api/storagedomains/abc" id="abc">
        <storage>
            <address>[fde4</address>
            <path>e66c</path>
        </storage>
    </storage_domain>
</storage_domains>


Expected results:

<storage_domains>
    <storage_domain href="/ovirt-engine/api/storagedomains/abc" id="abc">
        <storage>
            <address>[fde4:e66c:9a7c:dd91::1]</address>
            <path>/data/ovirt/data4</path>
        </storage>
    </storage_domain>
</storage_domains>

Additional info:
see mapFileDomain() in
ovirt-engine/backend/manager/modules/restapi/jaxrs/src/main/java/org/ovirt/engine/api/restapi/resource/BackendStorageDomainsResource.java

Comment 1 Dan Kenigsberg 2018-08-17 08:55:59 UTC
Hi Tal, may I *ask* to handle this sooner than later? This blocks deployment of hosted engine on top of an ipv6-only setup.

Comment 2 shani 2018-10-03 14:34:47 UTC
I've uploaded a patch: https://gerrit.ovirt.org/#/c/94673/.
Now parsing should look like:

<storage>
    <address>2620:52:0:2300:868f:69ff:fef9:5580</address>
    <nfs_version>auto</nfs_version>
    <path>/home/nfs_domains/my-nfs-ipv6</path>
    <type>nfs</type>
</storage>

Comment 3 shani 2018-10-24 13:30:12 UTC
Verified:

<storage>
<address>2620:52:0:2300:868f:69ff:fef9:6760</address>
<nfs_version>auto</nfs_version>
<path>/home/nfs_domains/nfs-carambola-ipv6</path>
<type>nfs</type>
</storage>

Comment 4 Sandro Bonazzola 2018-11-02 14:36:34 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

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