Description of problem: The network authentication checks in the tests/basic/mount-nfs-auth.t test depend on resolvable hostnames. When the test runs, the configuration is updated to allow/deny connections from $H0 (hostname --fqdn). In the case of running the tests in Vagrant with the ./run-tests-in-vagrant.sh script, the VMs do not get a resolvable IP address. The problem arises when the NFS-client connects to the Gluster/NFS server, and the server resolves the hostname of the client based on the IP-address. If the IP-address does not resolve to the configured $H0 hostname, access is denied and the testcase fails. Version-Release number of selected component (if applicable): mainline and 3.8 How reproducible: 100% Steps to Reproduce: 1. run ./run-tests-in-vagrant.sh 2. see mount-nfs-auth.t fail Actual results: mount-nfs-auth.t fails Expected results: mount-nfs-auth.t should pass Additional info: Bug 1350237 has been filed for a related problem that has been found while running the ./run-tests-in-vagrant.sh script.
Comment #1 in bug 1350237 has steps that I used in a VM to setup a DNS server for itself. Maybe this approach can be taken, or maybe there is a Vagrant plugin that can configure DNS correctly?
(In reply to Niels de Vos from comment #1) > Comment #1 in bug 1350237 ... https://bugzilla.redhat.com/show_bug.cgi?id=1350237#c1 because I dont know how to make Bugzilla render the link... Like bug 1350237#c1 maybe?
I think Vagrant on libvirt should provide you all you need. If not, I assume using Ansible could solve this.
These things are now fixed as we work with regression scripts properly in recent times (ie, haven't seen issues like this in a long time). Please feel free to reopen if still an issue.