Bug 1388501
| Summary: | 389-ds-base is missing runtime dependency - bind-utils | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.3 | CC: | enewland, mmuehlfe, msauton, nhosoi, nkinder, rmeggins, vashirov |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.5.10-12.el7 | Doc Type: | Bug Fix |
| Doc Text: |
The Directory Server setup script uses the "host" utility to look up host names and IP addresses. As a consequence, on systems that do not have the bind-utils package installed, the setup script fails. To fix the problem, bind-utils has been added as a dependency to the 389-ds-base package. As a result, the Directory Server setup script no longer fails because of a missing dependency.
|
Story Points: | --- |
| Clone Of: | 1386124 | Environment: | |
| Last Closed: | 2016-12-06 17:04:08 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: | |||
| Bug Depends On: | 1386124 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-10-25 13:59:21 UTC
Build tested: 389-ds-base-1.3.5.10-12.el7 [0 root@qeos-56 ~]# rpm -q bind-utils package bind-utils is not installed [0 root@qeos-56 ~]# rpm -q 389-ds-base package 389-ds-base is not installed [0 root@qeos-56 ~]# yum install 389-ds-base -y ... [0 root@qeos-56 ~]# rpm -q bind-utils bind-utils-9.9.4-37.el7.x86_64 [0 root@qeos-56 ~]# rpm -q 389-ds-base 389-ds-base-1.3.5.10-12.el7_3.x86_64 Marking as VERIFIED. 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-2879.html |