Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1273309

Summary: zonemgr email id should be checked before installation starts
Product: Red Hat Enterprise Linux 7 Reporter: Abhijeet Kasurde <akasurde>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED DUPLICATE QA Contact: Namita Soman <nsoman>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0CC: jcholast, mkosek, pvoborni, rcritten
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-05 09:53:06 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:
Attachments:
Description Flags
zonemgr_console.log none

Description Abhijeet Kasurde 2015-10-20 07:57:31 UTC
Description of problem:
If user specify command like 

ipa-server-install --setup-dns --forwarder=102.102.160.2  -r TESTRELM.TEST -p password -a password --zonemgr=Têko -U

installation goes on and while installation steps of DNS, it fails with error like following

<snip>

Configuring DNS (named)
  [1/12]: generating rndc key file
  [2/12]: adding DNS container
  [3/12]: setting up our zone
  [error] ConversionError: invalid 'admin_email': domain name 'Têko.redhat.com' should be normalized to: tãako.redhat.com
ipa.ipapython.install.cli.install_tool(Server): ERROR    invalid 'admin_email': domain name 'Têko.redhat.com' should be normalized to: tãako.redhat.com

</snip>

Version-Release number of selected component (if applicable):
ipa-server-4.2.0-15.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start fresh installation of IPA server with zonemgr option and unicode string as argument.

Actual results:
Installation fails at DNS configuration phase with 
ERROR    invalid 'admin_email': domain name 'Têko.redhat.com' should be normalized to: tãako.redhat.com

Expected results:
Installation should check before start and warn user beforehand.

Additional info:
Related to 
1. https://fedorahosted.org/freeipa/ticket/4771
2. https://bugzilla.redhat.com/show_bug.cgi?id=1163849

Comment 1 Abhijeet Kasurde 2015-10-20 07:59:42 UTC
Created attachment 1084647 [details]
zonemgr_console.log

Comment 3 Martin Bašti 2015-10-20 08:17:41 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5386

Comment 7 Petr Vobornik 2015-11-05 09:53:06 UTC

*** This bug has been marked as a duplicate of bug 1278330 ***