Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
(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 :(
(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"?
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
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