Bug 1469978
| Summary: | bind package is not automatically updated during ipa-server upgrade process | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Reznik <jreznik> |
| Component: | ipa | Assignee: | IPA Maintainers <ipa-maint> |
| Status: | CLOSED ERRATA | QA Contact: | ipa-qe <ipa-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | dkholia, enewland, jcholast, jreznik, ksiddiqu, lkimlick, mkosek, ndehadra, pemensik, pvoborni, pvomacka, rcritten, salmy, tkrizek, tscherf |
| Target Milestone: | rc | Keywords: | Regression, TestBlocker, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ipa-4.5.0-21.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Prior to this update, the bind packages were missing certain patches required by the bind-dyndb-ldap system plug-in. Consequently, the "named" service failed. To fix this bug, correct version of the bind packages has been used when installing bind-dyndb-ldap. As a result, correct bind package is installed.
|
Story Points: | --- |
| Clone Of: | 1469480 | Environment: | |
| Last Closed: | 2017-08-01 11:29:27 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: | 1469480 | ||
| Bug Blocks: | |||
|
Description
Jaroslav Reznik
2017-07-12 08:04:03 UTC
IPA-SERVER-VERSION:
ipa-server-4.5.0-21.el7.x86_64
BIND:
bind-9.9.4-51.el7.x86_64
bind-dyndb-ldap-11.1-4.el7.x86_64
Verified the bug on the basis of following observations:
1) Verified that IPA-server/replica is upgrade successfully.
2) Verified that bind package is updated successfully.
3) Verified that ipactl services are restarted correctly after the upgrade.
4) Verified the same for following upgrade paths:
- 7.3.z > 7.4
- 7.3 > 7.4
- 7.2.z > 7.4
- 7.1.z > 7.4
Details as below:
:: [ PASS ] :: Command 'yum -y update 'ipa*' sssd 'python*'' (Expected 0, got 0)
:: [ BEGIN ] :: Running 'tail -1 /var/log/ipaupgrade.log | grep 'The ipa-server-upgrade command was successful''
2017-07-13T11:18:34Z INFO The ipa-server-upgrade command was successful
:: [ PASS ] :: Command 'tail -1 /var/log/ipaupgrade.log | grep 'The ipa-server-upgrade command was successful'' (Expected 0, got 0)
:: [ BEGIN ] :: Running 'ipactl restart'
MARK-LWD-LOOP -- 2017-07-13 16:51:09 --
ipa: INFO: The ipactl command was successful
Restarting Directory Service
debugging enabled, suppressing output.
Restarting krb5kdc Service
Restarting kadmin Service
Restarting named Service
Restarting httpd Service
Restarting ipa-custodia Service
Restarting ntpd Service
Restarting pki-tomcatd Service
Restarting ipa-otpd Service
Restarting ipa-dnskeysyncd Service
:: [ PASS ] :: Command 'ipactl restart' (Expected 0, got 0)
:: [ BEGIN ] :: Running 'ipactl status'
ipa: INFO: The ipactl command was successful
Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
named Service: RUNNING
httpd Service: RUNNING
ipa-custodia Service: RUNNING
ntpd Service: RUNNING
pki-tomcatd Service: RUNNING
ipa-otpd Service: RUNNING
ipa-dnskeysyncd Service: RUNNING
:: [ PASS ] :: Command 'ipactl status' (Expected 0, got 0)
:: [ BEGIN ] :: Running 'service sssd restart'
Redirecting to /bin/systemctl restart sssd.service
:: [ PASS ] :: Command 'service sssd restart' (Expected 0, got 0)
:: [ BEGIN ] :: Running 'rpm -q ipa-server 389-ds-base bind bind-dyndb-ldap pki-ca sssd'
ipa-server-4.5.0-21.el7.x86_64
389-ds-base-1.3.6.1-16.el7.x86_64
bind-9.9.4-51.el7.x86_64
bind-dyndb-ldap-11.1-4.el7.x86_64
pki-ca-10.4.1-10.el7.noarch
sssd-1.15.2-50.el7.x86_64
:: [ PASS ] :: Command 'rpm -q ipa-server 389-ds-base bind bind-dyndb-ldap pki-ca sssd' (Expected 0, got 0)
Thus on the basis of above observations, marking status of bug to "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://access.redhat.com/errata/RHBA-2017:2327 *** Bug 1490816 has been marked as a duplicate of this bug. *** |