Bug 1375292

Summary: [docs] Glusterfs deployments will fail if gluster hostname does not resolve
Product: Red Hat Quickstart Cloud Installer Reporter: Fabian von Feilitzsch <fabian>
Component: doc-Technical_NotesAssignee: Julie <juwu>
Status: CLOSED CURRENTRELEASE QA Contact: James Olin Oden <joden>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0CC: bthurber, jlabocki, joden, juwu, tsanders
Target Milestone: gaKeywords: Triaged
Target Release: 1.0   
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: 2017-01-17 04:11:03 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 Fabian von Feilitzsch 2016-09-12 15:47:16 UTC
Description of problem:
If the hostname of a glusterfs server is not resolvable, deployments using glusterfs will fail, even if the server was specified by IP address.

To use glusterfs, users need to ensure that the hostname of the server is resolvable. They could add the entry to the Satellite DNS:
1. ssh to satellite machine
2. stop DNS

    /sbin/service named stop

3. Add the following line to /var/named/dynamic/db.example.com NOT the journal (jnl) files

    glusterfs        A     192.168.52.15

4. Restart

    /sbin/service named restart

5. Test

    ping glusterfs.example.com

They could also create an entry through the UI, by:
1. Go to Hosts -> New Host
2. Enter a name and specify a location for the host
3. Click Interfaces tab
4. Click edit on the interface already there
5. Add the mac address, fqdn, domain, and IP address of your gluster server
6. Click OK
7. Click the Operating System tab
8. Select the Architecture and OS of your gluster server
9. Unselect "Enable this host for provisioning"
10. Click submit

A warning will be displayed if the hostname of the gluster server is not specified. It will not prevent the user from continuing forward with a deployment, but it will probably result in a failed deployment later on.

Note:
The hostname of the gluster server MUST be resolvable, whether the user is specifying the share by IP address or hostname.