Previously, creating or editing an NFS storage domain's mount path so that the server's name ends in a digit (for example: myhost1:/path/to/data) was not allowed, meaning that legal host names could not be used as storage servers providing NFS storage to Red Hat Enterprise Virtualization. This limitation has now been removed so that hosts with names ending in digits can now be used as NFS servers.
## Description of problem:
In RHEV, admin UI rejects FQDNs ending in a digit when creating NFS storage domains
## Version-Release number of selected component (if applicable):
3.4, customer also reports this happening in 3.2
## How reproducible:
always
## Steps to Reproduce:
1. Create an NFS Data Center
2. On storage, create an appropriate NFS share
3. Via DNS create a domain that ends in a digit (ie: foo.example.f7) Or, just update /etc/hosts so that storage resolves to this name.
4. Try to create a storage domain with foo.example.f7:/<export>
## Actual results:
Attempt to create SD fails ("Error while executing action: Mount path is illegal, please use [IP:/path or FQDN:/path] convention.")
## Expected results:
Create SD as expected, with FQDN ending in a digit
## Additional info:
The workaround is to use the IP address, or short host name (assuming domain is in resolv.conf search path).
While this is an unusual domain name, It is to my knowledge valid [1], and I can't see any logical reason why it should be excluded.
[1] http://en.wikipedia.org/wiki/Domain_name#Technical_requirements_and_process
Technical insight:
This error doesn't come from the fortend (see test in http://gerrit.ovirt.org/#/c/30964/ that proves this point).
The failing validation comes from the backend in NfsMountPointConstraint.
Verified based on https://bugzilla.redhat.com/show_bug.cgi?id=1126342#c1
Ori 2014-08-13 09:56:16 EDT
verified on rc1
steps taken:
1.edit /etc/hosts file with FQDN that ends in a digit to an NFS domain ip
2.connect to that domain
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-0158.html
## Description of problem: In RHEV, admin UI rejects FQDNs ending in a digit when creating NFS storage domains ## Version-Release number of selected component (if applicable): 3.4, customer also reports this happening in 3.2 ## How reproducible: always ## Steps to Reproduce: 1. Create an NFS Data Center 2. On storage, create an appropriate NFS share 3. Via DNS create a domain that ends in a digit (ie: foo.example.f7) Or, just update /etc/hosts so that storage resolves to this name. 4. Try to create a storage domain with foo.example.f7:/<export> ## Actual results: Attempt to create SD fails ("Error while executing action: Mount path is illegal, please use [IP:/path or FQDN:/path] convention.") ## Expected results: Create SD as expected, with FQDN ending in a digit ## Additional info: The workaround is to use the IP address, or short host name (assuming domain is in resolv.conf search path). While this is an unusual domain name, It is to my knowledge valid [1], and I can't see any logical reason why it should be excluded. [1] http://en.wikipedia.org/wiki/Domain_name#Technical_requirements_and_process