Bug 712920 - DNS "A" record added to existing IPA server when using ipa-replica-prepare --ip-address
Summary: DNS "A" record added to existing IPA server when using ipa-replica-prepare --...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: freeIPA
Classification: Retired
Component: ipa-server
Version: 2.0
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Rob Crittenden
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-13 15:25 UTC by Sigbjorn Lie
Modified: 2015-01-04 23:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-14 12:32:49 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sigbjorn Lie 2011-06-13 15:25:59 UTC 
Description of problem:
When running ipa-replica-prepare with the "--ip-address" option using a subnet that does not have a reverse subnet configured on the IPA server, the IP address specified is added as a A record to the IPA server the ipa-replica-prepare script is run at. In my case, the first/primary installed IPA server.

Version-Release number of selected component (if applicable):
2.0 (F15)

How reproducible:
Every time

Steps to Reproduce:
1. Run ipa-replica-prepare with the "--ip-address" option, specify a subnet that's not already defined within the IPA servers DNS server.
2.
3.
  
Actual results:
An A record with the ip-address specified to the ipa-replica-prepare is added as an A record to the IPA server the ipa-replica-prepare command is run at.

Expected results:
An A record for the specified IP address should _not_ be added for the new replica's IP address.

Additional info:
Comment 1 Martin Kosek 2011-06-14 10:07:12 UTC 
Already fixed upstream in:
https://fedorahosted.org/freeipa/ticket/1223

Upstream commits:
master: 17c3f9e84efcbeb3b5ae1de83d799974de3bb078
ipa-2-0: 1df0ca7527aed9f2c445a9209066499bae0d07df
Comment 2 Jenny Severance 2011-06-14 12:32:49 UTC 
Closing bug - current version has the fix.
Comment 3 Martin Kosek 2011-06-14 13:43:07 UTC 
It is not fixed in current release but only upstream. The fix will be present in next Fedora release.
Note You need to log in before you can comment on or make changes to this bug.