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
Hi Tal, may I *ask* to handle this sooner than later? This blocks deployment of hosted engine on top of an ipv6-only setup.
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>
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>
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.