Bug 1319271

Summary:	auth.allow and auth.reject not working host mentioned with hostnames/FQDN
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	protocol	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Rochelle <rallan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, bkunal, moagrawa, nchilaka, olim, psony, rallan, rcyriac, rhinduja, rhs-bugs, rkavunga, sheggodu, srmukher, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.4.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	rebase
Fixed In Version:	glusterfs-3.12.2-1	Doc Type:	Bug Fix
Doc Text:	Previously, auth.allow or auth.reject options did not accept hostnames as values when provided with FQDN. However, with this fix, these options now accept hostnames when provided with FQDN.	Story Points:	---
Clone Of:
Clones:	1321578 (view as bug list)		Environment:
Last Closed:	2018-09-04 06:27:31 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:
Bug Depends On:	1546991
Bug Blocks:	1472361, 1503135

Description SATHEESARAN 2016-03-18 16:35:58 UTC

Description of problem:
-----------------------
auth.allow and auth.reject not taking in values of hostnames when mentioned with FQDNs, but works with IPv4

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHGS 3.1

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Set auth.allow or auth.reject with FQDN

Actual results:
---------------
auth.allow or auth.reject doesn't work with the hostnames when provided with FQDN 

Expected results:
-----------------
auth.allow or auth.reject should accept/respect the hostnames when provided with FQDN

Comment 4 Atin Mukherjee 2017-04-10 05:43:42 UTC

upstream patch : https://review.gluster.org/15086

Comment 12 errata-xmlrpc 2018-09-04 06:27:31 UTC

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://access.redhat.com/errata/RHSA-2018:2607

Comment 13 Red Hat Bugzilla 2023-09-14 23:59:15 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days