Bug 1386124

Summary: 389-ds-base is missing runtime dependency - bind-utils
Product: Red Hat Enterprise Linux 7 Reporter: Viktor Ashirov <vashirov>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.3CC: enewland, mreynolds, msauton, nkinder, rmeggins
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.6.1-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1388501 (view as bug list) Environment:
Last Closed: 2017-08-01 21:12:24 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:    
Bug Blocks: 1388501    

Description Viktor Ashirov 2016-10-18 08:43:00 UTC
Description of problem:
`host` utility is used in setup process to determine CNAME, but 389-ds-base rpm package doesn't depend on bind-utils, which contains it.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.5.10-11

How reproducible:
always

Steps to Reproduce:
1. echo "$IP_ADDRESS" test.example.com >> /etc/hosts
2. hostname test.example.com
3. setup-ds.pl

Actual results:
==============================================================================
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
<hostname>.<domainname>
Example: eros.example.com.

To accept the default shown in brackets, press the Enter key.

Warning: This step may take a few minutes if your DNS servers
can not be reached or if DNS is not configured correctly.  If
you would rather not wait, hit Ctrl-C and run this program again
with the following command line option to specify the hostname:

    General.FullMachineName=your.hostname.domain.name

Computer name [test.example.com]: 
sh: /usr/bin/host: No such file or directory                                  <=============

WARNING: There are problems with the hostname.
Hostname 'test.example.com' is valid, but none of the IP addresses
resolve back to test.example.com
- address 172.16.36.137 resolves to host qeos-137.lab.eng.rdu2.redhat.com

Please check the spelling of the hostname and/or your network configuration.
If you proceed with this hostname, you may encounter problems.

Do you want to proceed with hostname 'test.example.com'? [no]:

Expected results:
bind-utils should be installed as a dependency for 389-ds-base.

Additional info:
This dependency was introduced in bz1276072 and https://fedorahosted.org/389/ticket/48328

Comment 1 Noriko Hosoi 2016-10-18 16:10:19 UTC
Thanks for finding out this problem, Viktor!

Is it ok to release this fix as part of 7.3.z?

Comment 2 Viktor Ashirov 2016-10-18 16:16:32 UTC
(In reply to Noriko Hosoi from comment #1)
> Thanks for finding out this problem, Viktor!
> 
> Is it ok to release this fix as part of 7.3.z?
I think so, since it's a part of RFE. And without this dependency it won't work.
Too bad I found it so late :(

Comment 3 Noriko Hosoi 2016-10-18 17:43:18 UTC
(In reply to Viktor Ashirov from comment #2)
> (In reply to Noriko Hosoi from comment #1)
> > Thanks for finding out this problem, Viktor!
> > 
> > Is it ok to release this fix as part of 7.3.z?
> I think so, since it's a part of RFE. And without this dependency it won't
> work.
> Too bad I found it so late :(

Oh, I am sorry not to notice it...  But definitely, better than not-found, isn't it?

Shall we add this to the relnotes to ask customers to run "yum install bind-utils"?

Comment 4 Marc Sauton 2016-10-25 01:01:13 UTC
GSS Approved Z-Stream

Comment 7 Viktor Ashirov 2017-04-06 10:59:01 UTC
Build tested:
389-ds-base-0:1.3.6.1-6.el7.x86_64

$ repoquery --requires --resolve 389-ds-base | grep bind
bind-utils-32:9.9.4-44.el7.x86_64

Marking as VERIFIED.

Comment 8 errata-xmlrpc 2017-08-01 21:12:24 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/RHBA-2017:2086