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.
Bug 709332 - IPA Replica Installation Fails - reverse address doesn't match error
Summary: IPA Replica Installation Fails - reverse address doesn't match error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On: 704012
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-31 12:17 UTC by Ken Reilly
Modified: 2015-01-04 23:49 UTC (History)
11 users (show)

Fixed In Version: ipa-2.0.0-23.el6_1.1
Doc Type: Bug Fix
Doc Text:
When a new reverse zone is created via the ipa-replica-prepare script, the wrong DNS entry is updated, which eventually causes an installation of a replica server to fail. To get the correct DNS entries set up when creating a replica package for an installation of a replica server, restart named service after creating replica package.
Clone Of:
Environment:
Last Closed: 2011-06-15 00:22:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0865 0 normal SHIPPED_LIVE ipa bug fix update 2011-06-15 00:21:53 UTC

Description Ken Reilly 2011-05-31 12:17:03 UTC 
This bug has been copied from bug #704012 and has been proposed
to be backported to 6.1 z-stream (EUS).
Comment 4 Tomas Capek 2011-06-06 09:56:00 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When a new reverse zone was created via the ipa-replica-prepare script, the wrong DNS entry was updated, which eventually caused an installation of a replica server to fail. This bug has been fixed and the correct DNS entries are now set up when creating a replica package for an installation of a replica server.
Comment 5 Namita Soman 2011-06-10 12:09:13 UTC 
Tested using ipa-server-2.0.0-23.el6_1.1.x86_64 

The replica install fails with same error.
ERROR    The DNS forward record apollo.testrelm. does not match the reverse address apollo.idm.lab.bos.redhat.com.

Can install replica, if i follow steps below -
on master, create replica pkg
on master, restart named service
on slave, run install
Comment 6 Martin Kosek 2011-06-10 12:24:32 UTC 
I think this is OK. The steps you described including named restart are needed. If the named service is not restarted, it won't serve the new DNS zone created during ipa-replica-prepare.
Comment 7 Namita Soman 2011-06-10 13:27:38 UTC 
So went back to starting named after creatign replica package. Can install replica successfully. Also verified 

output for command below:
#ipa dnsrecord-find --all

includes among other records, the below:
dn: idnsname=apollo,idnsname=testrelm,cn=dns,dc=testrelm
  Record name: apollo
  A record: 10.16.96.78
  objectclass: top, idnsrecord



where master is running on apollo. and this does not include an A record for the replica ip, as expected.

updated technical notes with proposed edits - to indicate that named service should be restarted for replica install to succeed, if it is in a different zone
Comment 8 Namita Soman 2011-06-10 13:27:38 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When a new reverse zone was created via the ipa-replica-prepare script, the wrong DNS entry was updated, which eventually caused an installation of a replica server to fail. This bug has been fixed and the correct DNS entries are now set up when creating a replica package for an installation of a replica server.+When a new reverse zone is created via the ipa-replica-prepare script, the wrong DNS entry is updated, which eventually causes an installation of a replica server to fail. To get the correct DNS entries set up when creating a replica package for an installation of a replica server, restart named service after creating replica package.
Comment 9 errata-xmlrpc 2011-06-15 00:22:11 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0865.html
Note You need to log in before you can comment on or make changes to this bug.