Bug 1292649

Summary:	DSUtil.pm - allow users to specify to relax the FQDN constraint
Product:	Red Hat Enterprise Linux 6	Reporter:	Noriko Hosoi <nhosoi>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED ERRATA	QA Contact:	Viktor Ashirov <vashirov>
Severity:	unspecified	Docs Contact:	Petr Bokoc <pbokoc>
Priority:	unspecified
Version:	6.0	CC:	amsharma, jgalipea, nkinder, pbokoc, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-72.el6	Doc Type:	Bug Fix
Doc Text:	When creating a server instance, the setup script checks that the FQDN can be strictly resolved. But there is a requirent the constraint is not necessary. To solve the problem, an option to relax the constraint is added. If "General.StrictHostCheck=false", setup script accepts the host name specified by General.FullMachineName without checking the name against the DNS server.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-10 19:22:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Noriko Hosoi 2015-12-18 00:36:04 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/48332

When creating a server instance, DSUtil::checkHostname checks that the FQDN can be strictly resolved.

It is necessary for the Admin Server installation via setup-ds-admin.pl, but there could be a case the constraint is not necessary.  That said, it should be useful to add an option to relax the constraint.

Comment 1 Viktor Ashirov 2016-01-03 21:08:38 UTC

New option should be documented. Doc bug added: bz1295235

Comment 6 errata-xmlrpc 2016-05-10 19:22: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://rhn.redhat.com/errata/RHBA-2016-0737.html