I wanted to try out adding a storage domain over IPv6 and simply copied an NFS export path from the command line, with a trailing slash (because I used tab completion). I pasted this address into the "New Domain" dialog's "Export Path" entry: [fd8f:1391:3a82:200::c0a8:c8e2]:/exports/nfs/share1/ The path was not accepted. I got the following message: "NFS mount path is illegal, please use [IP:/path or FQDN:/path] convention." This lead me to believe that IPv6 NFS paths were not accepted. Later, I found that they actually are, as https://bugzilla.redhat.com/show_bug.cgi?id=1302358 is already fixed. Please allow trailing slashes in NFS export paths to avoid user confusion, or introduce a more explanatory error message in case slash-final paths are discouraged (but I don't see a reason for that).
*** Bug 1468911 has been marked as a duplicate of this bug. ***
Created attachment 1295785 [details] Failing tests for / only mount paths The attached patches improve the situation, but don't handle mount paths like myserver.com:/ I'm attaching example tests that fail with them.
Overzealously moved to MODIFIED, returning to POST
-------------------------------------- Tested with the following code: ---------------------------------------- ovirt-engine-4.2.0-0.0.master.20170728194615.gitec6aa15.el7.centos.noarch vdsm-4.20.1-269.git4afc67d.el7.centos.x86_64 Tested with the following scenario: Steps to Reproduce: 1. create new storage domain with trailing slash at the end of the path Actual results: storage domain was added successfully Expected results: Moving to VERIFIED!
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.