Bug 1283943
| Summary: | IPA DNS Zone/DNS Forward Zone details missing after upgrade from RHEL 7.0 to RHEL 7.2 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Nikhil Dehadrai <ndehadra> | |
| Component: | ipa | Assignee: | Martin Bašti <mbasti> | |
| Status: | CLOSED ERRATA | QA Contact: | Namita Soman <nsoman> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 7.2 | CC: | ekeck, jcholast, jkurik, ksiddiqu, mbasti, mkosek, pspacek, pvoborni, rcritten | |
| Target Milestone: | rc | Keywords: | Regression, ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | ipa-4.2.0-16.el7 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1284052 (view as bug list) | Environment: | ||
| Last Closed: | 2016-11-04 05:41:03 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: | 1284052 | |||
|
Description
Nikhil Dehadrai
2015-11-20 11:12:59 UTC
Upstream ticket: https://fedorahosted.org/freeipa/ticket/5472 Original dns forward zones has to be migrated to new forward zones during upgrade. Otherwise the forward zones will not work as expected with bind-dyndb-ldap. Fail during upgrade causes that the original forward zones were removed (it has to be in every case) but due to bug in dnszone-del code, removal has not been finished properly, thus no new forward zones have been recreated. Impact: forward zones will be removed which may break a customer configuration. This happen only with RHEL 7.0 -> 7.2 upgrade, this migration upgrade is not executed during 7.1 -> 7.2 upgrade. Workaround: Unknown, forward zones must be added back to IPA manually Upgrade did backup of original DNS zone data which has to be migrated to IPA as forwardzones. Fixed upstream master: https://fedorahosted.org/freeipa/changeset/72b03a5d7931635b8563e374f217fa48c729450b ipa-4-2: https://fedorahosted.org/freeipa/changeset/68eef6c21f3fa0f1351f420d20f5cea93dac64ec Fixed upstream master: https://fedorahosted.org/freeipa/changeset/6eeb4e4f2a9fb6fe5cf83e6b84c737ad3e295de1 ipa-4-2: https://fedorahosted.org/freeipa/changeset/8b0f60fbfb5192a8dde2b459d9d15ab11337cf66 IPA server version: ipa-server-4.4.0-5.el7.x86_64 Tested the bug on the basis of following steps: 1. Noticed that IPA DNS Zone/DNS Forward Zone details are not found after upgrade from 7.0 to 7.3. 2. See below for console output logs. [root@vm-idm-004 ~]# ipa dnszone-find ipa: ERROR: 2.114 client incompatible with 2.65 server at 'https://<ipa-server-hostname>/ipa/xml' [root@vm-idm-004 ~]# kinit admin Password for admin: [root@vm-idm-004 ~]# ipa dnszone-find ipa: ERROR: 2.114 client incompatible with 2.65 server at 'https://<ipa-server-hostname>/ipa/xml' [root@vm-idm-004 ~]# ipa dnsforwardzone-find ipa: ERROR: unknown command 'dnsforwardzone_find' [root@vm-idm-004 ~]# rpm -q ipa-server ipa-server-4.4.0-5.el7.x86_64 Thus on the basis of above observations marking the status of bugs to "ASSIGNED" Honza, could you tell us what is the probable cause of problem mentioned in comment #13? I'm quite sure that it is not related to DNS :-) Same error was seen also in bug 1365507. I suspect same cause, probably missing restart of httpd service in the upgrade. Yes, that seems to be the cause. moving back to on QA as the issue in comment 13 should be fixed in bug 1365572 IPA server version: ipa-server-4.4.0-10.el7.x86_64 Verified that after updating ipa server hosted on RHEL 7.0 to RHEL 7.3, then 'ipa dnszone-find' and 'ipa dnsforwardzone-find' coomands are successfully run and error mention above in comment#13 is not observed. Thus marking the 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://rhn.redhat.com/errata/RHBA-2016-2404.html |