Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1350238

Summary:	Vagrant environment for tests should configure DNS for VMs
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	tests	Assignee:	bugs <bugs>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	atumball, bugs, rtalur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-09 19:58:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Niels de Vos 2016-06-26 16:41:17 UTC

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 Niels de Vos 2016-06-27 09:11:24 UTC

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?

Comment 2 Niels de Vos 2016-06-27 09:12:28 UTC

(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?

Comment 3 Yaniv Kaul 2019-04-17 11:42:21 UTC

I think Vagrant on libvirt should provide you all you need.
If not, I assume using Ansible could solve this.

Comment 4 Amar Tumballi 2019-05-09 19:58:51 UTC

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.