Description of problem: When creating a new Storage Domain, the export path cannot be edited with an IPv6 address. The format should be [IPv6 Address]:/path, e.g [201::1]:/path Version-Release number of selected component (if applicable): Latest How reproducible: Try to add a new storage domain with an IPv6 address/ Steps to Reproduce: 1. Open Storage tab. 2. Click New Domain 3. Edit in 'Export Path' textbox something like: [201::1]:/my/folder 4. Try to add the domain. Actual results: Error on the textbox: NFS mount path is illegal... Expected results: To accept the address and connect to the storage. Additional info: Should work with all storage types. It is part of the IPv6 task. With an FQDN that points to an IPv6 address, it works fine.
*** Bug 1302356 has been marked as a duplicate of this bug. ***
org.ovirt.engine.ui.uicommonweb.validation.LinuxMountPointValidation should be updated in order to validate IPv6 containing URLs properly.
It looks like this bug is only about the webadmin for some reason. If I got it right, it is not possible to add a file domain using an ipv6 address at all, and not only via the webadmin. Am I right? Or have I got it wrong when trying to do it via the REST API? If I am wrong, can you give an example for a REST API call to add an file domain?
The problem seems to reside in vdsm. Updating the BZ.
In more details: It seems that oop.getProcessPool(possibleDomain)... in fileSD - scanDomains -> collectMetaFile doesn't return the metaFiles because the '[' and ']' are not escaped. The exact same bug occurred when I tried to create a domain with a name like "the[new]sd". We need to escape the '[]' characters because when trying to find what the sd dir contains I think that vdsm treats the '[]' as a part of a regex, and since it cannot find the dir it complains that the storage domain does not exist.
Until this bug was solved, file domains could not be created using IPV6 addresses. Therefore, this will probably require creating new automation tests by QE. Raz, can you please make sure that it happens?
Sure
IPv6 export path is accepted. ConnectStorageServer is executed using the correct path including the IPv6 address of the NFS server. 2017-03-12 13:32:15,311+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (default task-28) [b6c72be6-776b-4b6c-a044-f80317eed34e] START, ConnectStorageServerVDSCommand(HostName = host_mixed_1, StorageServerConnectionManagementVDSParameters:{runAsync='true', hostId='652a6dec-7c2d-423e-9b9b-abcb4c29d04f', storagePoolId='00000000-0000-0000-0000-000000000000', storageType='NFS', connectio nList='[StorageServerConnections:{id='null', connection='[fe80::21b:21ff:fe75:35fb]:/Storage_NFS/elad/2', iqn='null', vfsType='null', mountOptions='null', nfsVersion='AUTO', nfsRetrans='null', nfsTimeo='null', i face='null', netIfaceName='null'}]'}), log id: 33dd9a16 Used: rhevm-4.1.1.3-0.1.el7.noarch vdsm-4.19.7-1.el7ev.x86_64