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 1353909 - The ipa-dns-install command failed, exception: ValueError: DNS zone ... already exists in DNS
Summary: The ipa-dns-install command failed, exception: ValueError: DNS zone ... alrea...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Florence Blanc-Renaud
QA Contact: Kaleem
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-08 11:42 UTC by Sudhir Menon
Modified: 2021-08-19 07:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-19 07:31:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sudhir Menon 2016-07-08 11:42:10 UTC 
Description of problem: "The ipa-dns-install command failed, exception: ValueError:" when DNS service is running on different machine and the command is executed.

Version-Release number of selected component (if applicable):
ipa-server-dns-4.4.0-1.el7.noarch
ipa-server-4.4.0-1.el7.x86_64

How reproducible: Always

Steps to Reproduce:

1. DNS for IPA domain is setup on remote windows machine.
2. Ensure /etc/resolv.conf of IPA server points to windows machine.
3. Install IPA server without integrated DNS.
4. Now run ipa-dns-install command
5. Check the message displayed on the console.

Actual results:
The log file for this installation can be found in 
/var/log/ipaserver-install.log
Checking DNS domain testrelm.test., please wait ...
Unexpected error - see /var/log/ipaserver-install.log for details:
ValueError: DNS zone testrelm.test. already exists in DNS and is handled by server(s): apache.pne.qe.

===/var/log/ipaserver-install.log===
2016-07-08T11:24:41Z DEBUG raw: dns_is_enabled(version=u'2.210')
2016-07-08T11:24:41Z DEBUG dns_is_enabled(version=u'2.210')
2016-07-08T11:24:41Z DEBUG retrieving schema for SchemaCache url=ldapi://%2fvar%2frun%2fslapd-TESTRELM-TEST.socket conn=<ldap.ldapobject.SimpleLDAPObject instance at 0x6173cf8>
2016-07-08T11:24:41Z INFO Checking DNS domain testrelm.test., please wait ...
2016-07-08T11:24:41Z DEBUG   File "/usr/lib/python2.7/site-packages/ipaserver/install/installutils.py", line 752, in run_script
    return_value = main_function()
File "/usr/sbin/ipa-dns-install", line 148, in main
dns_installer.install_check(True, api, False, options, hostname=api.env.host)
File "/usr/lib/python2.7/site-packages/ipaserver/install/dns.py", line 128, in install_check
raise e
2016-07-08T11:24:41Z DEBUG The ipa-dns-install command failed, exception: ValueError: DNS zone testrelm.test. already exists in DNS and is handled by server(s): apache.pne.qe.

Expected results:
Instead of throwing value error on the console, proper message should be displayed on the console e.g 

ipa-dns-install command failed: DNS zone testrelm.test. already exists in DNS and is handled by server(s): apache.pne.qe.

Additional info:
Comment 1 Petr Vobornik 2016-07-08 11:59:59 UTC 
Seems to me that it is expected - zone overlap check, right Petr?
Comment 2 Petr Spacek 2016-07-08 12:10:46 UTC 
Yes, this is expected. The message clearly says where the problem is - the user used invalid parameter values in the installer.


If I understand Sudhir correctly this bug is about replacing this message:

Unexpected error - see /var/log/ipaserver-install.log for details:
ValueError: DNS zone testrelm.test. already exists in DNS and is handled by server(s): apache.pne.qe.


with message:

ipa-dns-install command failed: DNS zone testrelm.test. already exists in DNS and is handled by server(s): apache.pne.qe.


Is that right?
Comment 3 Sudhir Menon 2016-07-08 12:22:20 UTC 
Petr,
Yes the bug is about replacing message displayed on console with proper message rather than ValueError/Unexpected error.
Comment 5 Petr Vobornik 2016-07-12 16:11:38 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/6067
Comment 6 Petr Vobornik 2016-07-12 16:12:53 UTC 
Affected code is fragile, there is a risk that fix can break other stuff therefore postponing so that it can live in upstream for a while.
Comment 12 Florence Blanc-Renaud 2020-02-14 14:53:05 UTC 
Thank you taking your time and submitting this request for Red Hat Enterprise Linux 7. Unfortunately, this bug cannot be kept even as a stretch goal and was postponed to RHEL8.
Comment 19 RHEL Program Management 2021-08-19 07:31:10 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.