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 742875 - named fails to start after installing ipa server when short hostname preceeds fqdn in /etc/hosts.
Summary: named fails to start after installing ipa server when short hostname preceeds...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.2
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 748554
TreeView+ depends on / blocked
 
Reported: 2011-10-03 08:13 UTC by Gowrishankar Rajaiyan
Modified: 2023-11-08 04:25 UTC (History)
9 users (show)

Fixed In Version: ipa-2.1.3-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: When IPA server is installed, it does not check properly system's static lookup table (/etc/hosts) for records that may interfere with its IP address or hostname. Consequence: If /etc/hosts contains records with IP address or hostname matching the one configured for IPA, the IPA server installation may crash later during the installation process as forward or reverse DNS queries resolves to different values than expected. Fix: ipa-server-install now always checks if there is a conflicting record in /etc/hosts and reports a clean error if there is any Result: ipa-server-install won't crash because of conflicting records in /etc/hosts
Clone Of:
Environment:
Last Closed: 2011-12-06 18:33:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-8034 0 None None None 2022-03-21 09:14:35 UTC
Red Hat Product Errata RHSA-2011:1533 0 normal SHIPPED_LIVE Moderate: ipa security and bug fix update 2011-12-06 01:23:31 UTC

Description Gowrishankar Rajaiyan 2011-10-03 08:13:30 UTC 
Description of problem:
After installing ipa-server with --setup-dns, if you have the short hostname ahead of fqdn in /etc/hosts, named fails to start. sssd tries to do a GSSAPI auth with the short hostname and does not find its respective principal in kerberos. Setting `hostname -s` at the end solves this issue.

Version-Release number of selected component (if applicable):
sssd-1.5.1-53.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure your /etc/hosts as 
[root@jetfire ]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost6 localhost6.localdomain6
2620:52:0:41c9:5054:ff:fea8:b669	jetfire jetfire.lab.eng.pnq.redhat.com

2. Install ipa-server
<snip>
Configuring named:
  [1/9]: adding DNS container
  [2/9]: setting up our zone
  [3/9]: setting up reverse zone
  [4/9]: setting up our own record
  [5/9]: setting up kerberos principal
  [6/9]: setting up named.conf
  [7/9]: restarting named
named service failed to start              <<<<<<<<<<<<<<
  [8/9]: configuring named to start on boot
  [9/9]: changing resolv.conf to point to ourselves
done configuring named.
</snip>

3. service named resart
# service named restart
Stopping named:                                            [  OK  ]
Starting named:                                            [FAILED]

  
Actual results: named fails to start. named starts successfully when I set the fqdn followed by `hostname -s` in /etc/hosts. 


Expected results: named should start successfully even when `hostname -s` preceeds fqdn in /etc/hosts. In RHEL6.2 the default /etc/hosts looks like:
# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

So, it would be quite common for users to add `hostname -s` ahead of fqdn as that is how we specify for localhost.

Additional info:

/var/log/messages:
Oct  3 03:03:06 jetfire named[15335]: starting BIND 9.7.3-P3-RedHat-9.7.3-7.P3.el6 -u named
Oct  3 03:03:06 jetfire named[15335]: built with '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu' '--target=x86_64-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib64' '--libexecdir=/usr/libexec' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-libtool' '--localstatedir=/var' '--enable-threads' '--enable-ipv6' '--with-pic' '--disable-static' '--disable-openssl-version-check' '--with-dlz-ldap=yes' '--with-dlz-postgres=yes' '--with-dlz-mysql=yes' '--with-dlz-filesystem=yes' '--with-gssapi=yes' '--disable-isc-spnego' '--with-docbook-xsl=/usr/share/sgml/docbook/xsl-stylesheets' 'build_alias=x86_64-redhat-linux-gnu' 'host_alias=x86_64-redhat-linux-gnu' 'target_alias=x86_64-redhat-linux-gnu' 'CFLAGS= -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' 'CPPFLAGS= -DDIG_SIGCHASE'
Oct  3 03:03:06 jetfire named[15335]: adjusted limit on open files from 1024 to 1048576
Oct  3 03:03:06 jetfire named[15335]: found 1 CPU, using 1 worker thread
Oct  3 03:03:06 jetfire named[15335]: using up to 4096 sockets
Oct  3 03:03:06 jetfire named[15335]: loading configuration from '/etc/named.conf'
Oct  3 03:03:06 jetfire named[15335]: using default UDP/IPv4 port range: [1024, 65535]
Oct  3 03:03:06 jetfire named[15335]: using default UDP/IPv6 port range: [1024, 65535]
Oct  3 03:03:06 jetfire named[15335]: listening on IPv6 interfaces, port 53
Oct  3 03:03:06 jetfire named[15335]: listening on IPv4 interface lo, 127.0.0.1#53
Oct  3 03:03:06 jetfire named[15335]: generating session key for dynamic DNS
===============================
Oct  3 03:03:06 jetfire sssd_be: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (Server ldap/jetfire.PNQ.REDHAT.COM not found in Kerberos database)
Oct  3 03:03:16 jetfire named[15335]: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (Server ldap/jetfire.PNQ.REDHAT.COM not found in Kerberos database)
===============================
Oct  3 03:03:16 jetfire named[15335]: bind to LDAP server failed: Local error
Oct  3 03:03:16 jetfire named[15335]: loading configuration: failure
Oct  3 03:03:16 jetfire named[15335]: exiting (due to fatal error)


/var/log/sssd/sssd_lab.eng.pnq.redhat.com.log:
(Mon Oct  3 03:03:05 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sbus_dispatch] (9): dbus conn: 24C3850
(Mon Oct  3 03:03:05 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sbus_dispatch] (9): Dispatching.
(Mon Oct  3 03:03:05 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sbus_message_handler] (9): Received SBUS method [ping]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sbus_dispatch] (9): dbus conn: 24D6990
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sbus_dispatch] (9): Dispatching.
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sbus_message_handler] (9): Received SBUS method [getAccountInfo]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [be_get_account_info] (4): Got request for [4099][1][name=named]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [be_get_account_info] (4): Request processed. Returned 1,11,Fast reply - offline
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_id_op_connect_step] (9): beginning to connect
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [fo_resolve_service_send] (4): Trying to resolve service 'IPA'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_server_status] (7): Status of server 'jetfire.lab.eng.pnq.redhat.com' is 'name resolved'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_port_status] (7): Port status of port 0 for server 'jetfire.lab.eng.pnq.redhat.com' is 'not working'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_port_status] (4): Reseting the status of port 0 for server 'jetfire.lab.eng.pnq.redhat.com'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_server_status] (7): Status of server 'jetfire.lab.eng.pnq.redhat.com' is 'name resolved'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [be_resolve_server_done] (4): Found address for server jetfire.lab.eng.pnq.redhat.com: [2620:52:0:41c9:5054:ff:fea8:b669] TTL 7200
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [ipa_resolve_callback] (6): Constructed uri 'ldap://jetfire.lab.eng.pnq.redhat.com'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sss_ldap_init_send] (9): Using file descriptor [27] for LDAP connection.
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_ldap_connect_callback_add] (9): New LDAP connection to [ldap://jetfire.lab.eng.pnq.redhat.com:389/??base] with fd [27].
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_rootdse_send] (9): Getting rootdse
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (6): calling ldap_search_ext with [(objectclass=*)][].
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [*]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [altServer]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [namingContexts]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [supportedControl]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [supportedExtension]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [supportedFeatures]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [supportedLDAPVersion]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [supportedSASLMechanisms]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [defaultNamingContext]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [lastUSN]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (7): Requesting attrs: [highestCommittedUSN]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_step] (8): ldap_search_ext called, msgid = 1
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_process_result] (8): Trace: sh[0x24e6b10], connected[1], ops[0x24d9050], ldap[0x24e7890]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_parse_entry] (9): OriginalDN: [].
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_process_result] (8): Trace: sh[0x24e6b10], connected[1], ops[0x24d9050], ldap[0x24e7890]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_generic_done] (6): Search result: Success(0), (null)
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_rootdse_done] (9): Got rootdse
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_kinit_send] (6): Attempting kinit ((null), host/jetfire.lab.eng.pnq.redhat.com, LAB.ENG.PNQ.REDHAT.COM, 86400)
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_kinit_next_kdc] (7): Resolving next KDC for service IPA
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [fo_resolve_service_send] (4): Trying to resolve service 'IPA'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_server_status] (7): Status of server 'jetfire.lab.eng.pnq.redhat.com' is 'name resolved'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_port_status] (7): Port status of port 0 for server 'jetfire.lab.eng.pnq.redhat.com' is 'neutral'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_server_status] (7): Status of server 'jetfire.lab.eng.pnq.redhat.com' is 'name resolved'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [be_resolve_server_done] (4): Found address for server jetfire.lab.eng.pnq.redhat.com: [2620:52:0:41c9:5054:ff:fea8:b669] TTL 7200
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_kinit_kdc_resolved] (7): KDC resolved, attempting to get TGT...
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [create_tgt_req_send_buffer] (7): buffer size: 73
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [child_handler_setup] (8): Setting up signal handler up for pid [15334]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [child_handler_setup] (8): Signal handler set up for pid [15334]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [set_tgt_child_timeout] (6): Setting 6 seconds timeout for tgt child
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_process_result] (8): Trace: sh[0x24e6b10], connected[1], ops[(nil)], ldap[0x24e7890]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_process_result] (8): Trace: ldap_result found nothing!
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [write_pipe_handler] (6): All data has been sent!
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [read_pipe_handler] (6): EOF received, client finished
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_get_tgt_recv] (6): Child responded: 0 [FILE:/var/lib/sss/db/ccache_LAB.ENG.PNQ.REDHAT.COM], expired on [1317711786]
===============================
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sasl_bind_send] (4): Executing sasl bind mech: GSSAPI, user: host/jetfire.lab.eng.pnq.redhat.com
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sasl_bind_send] (1): ldap_sasl_bind failed (-2)[Local error]
===============================
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [child_sig_handler] (7): Waiting for child [15334].
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [child_sig_handler] (4): child [15334] finished successfully.
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [fo_set_port_status] (4): Marking port 0 of server 'jetfire.lab.eng.pnq.redhat.com' as 'not working'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_handle_release] (8): Trace: sh[0x24e6b10], connected[1], ops[(nil)], ldap[0x24e7890], destructor_lock[0], release_memory[0]
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [remove_connection_callback] (9): Successfully removed connection callback.
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_id_op_connect_done] (9): attempting failover retry on op #1
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_id_op_connect_step] (9): beginning to connect
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [fo_resolve_service_send] (4): Trying to resolve service 'IPA'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_server_status] (7): Status of server 'jetfire.lab.eng.pnq.redhat.com' is 'name resolved'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [get_port_status] (7): Port status of port 0 for server 'jetfire.lab.eng.pnq.redhat.com' is 'not working'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [fo_resolve_service_send] (1): No available servers for service 'IPA'
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_id_release_conn_data] (9): releasing unused connection
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_id_op_connect_done] (1): Failed to connect, going offline (5 [Input/output error])
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [be_mark_offline] (8): Going offline!
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [be_run_offline_cb] (3): Going offline. Running callbacks.
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_id_op_connect_done] (9): notify offline to op #1
(Mon Oct  3 03:03:06 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [sdap_id_release_conn_data] (9): releasing unused connection
(Mon Oct  3 03:03:07 2011) [sssd[be[lab.eng.pnq.redhat.com]]] [remove_krb5_info_files] (5): Could not remove [/var/lib/sss/pubconf/kpasswdinfo.LAB.ENG.PNQ.REDHAT.COM], [2][No such file or directory]
Comment 2 Jakub Hrozek 2011-10-03 10:14:33 UTC 
I don't think this is a bug (and definitely not SSSD bug). 

If I recall correctly, IPA requires that the IPA server hostname is a FQDN and reverse DNS resolutions works correctly.

Shanks, what does "getent hosts 2620:52:0:41c9:5054:ff:fea8:b669" say?

Martin, can you confirm?
Comment 3 Martin Kosek 2011-10-03 10:41:46 UTC 
Yes, IPA requires a hostname to be a FQDN. This is setting of /etc/hosts is invalid.

IPA server shouldn't even configure successfully if you configure /etc/hosts this way before calling ipa-server-install.
Comment 4 Jakub Hrozek 2011-10-03 10:56:59 UTC 
Thank you, Martin. Closing as NOTABUG as per comment #3.
Comment 5 Stephen Gallagher 2011-10-03 11:16:24 UTC 
Per comment #3, shouldn't the actual bug be that ipa-server-install should detect this configuration and should fail to install.
Comment 6 Jakub Hrozek 2011-10-03 11:28:57 UTC 
I understood that Shanks changed /etc/hosts post-install, but if IPA actually installed with /etc/hosts that list short host name first..that is a bug.
Comment 7 Martin Kosek 2011-10-03 11:42:02 UTC 
(In reply to comment #5)
> Per comment #3, shouldn't the actual bug be that ipa-server-install should
> detect this configuration and should fail to install.

Yes, ipa-server-install will fail if the /etc/hosts is configured this way. I was under the same impression as Jakub that Shanks did the change post-install.
Comment 8 Gowrishankar Rajaiyan 2011-10-03 12:11:28 UTC 
/etc/hosts was set before ipa-server-install. I just tried it again.

# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost6 localhost6.localdomain6
2620:52:0:41c9:5054:ff:fea8:b669	jetfire	jetfire.lab.eng.pnq.redhat.com


# ipa-server-install --setup-dns --no-forwarders --hostname=jetfire.lab.eng.pnq.redhat.com  -r LAB.ENG.PNQ.REDHAT.COM -n lab.eng.pnq.redhat.com -p Secret123 -P Secret123 -a Secret123 -U

<snip>
done configuring httpd.
Applying LDAP updates
Restarting the directory server
Restarting the KDC
Restarting the web server
Configuring named:
  [1/9]: adding DNS container
  [2/9]: setting up our zone
  [3/9]: setting up reverse zone
  [4/9]: setting up our own record
  [5/9]: setting up kerberos principal
  [6/9]: setting up named.conf
  [7/9]: restarting named
named service failed to start
  [8/9]: configuring named to start on boot
  [9/9]: changing resolv.conf to point to ourselves
done configuring named.
==============================================================================
Setup complete
</snip>
Comment 9 Martin Kosek 2011-10-04 12:51:41 UTC 
Ah, yes, I see the bug picture now. When ipa-server-install is run with --setup-dns or --no-host-dns, no DNS check is run by design and a warning is reported by ipa-server-install.
Comment 10 Dmitri Pal 2011-10-04 14:42:00 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1923
Comment 11 Rob Crittenden 2011-10-13 22:05:58 UTC 
master:
363c23a37c3631a0fb16df6b88bd5138677b818a
9bff6cb8a955c3f4b167e05856b40f6e2ee5dca8

ipa-2-1:
58918c4593fed9d546368483d4509798fbaa9322
93feb5293236a5d0e22ae15eee35e7b9eb93e6e4
Comment 13 Gowrishankar Rajaiyan 2011-10-25 04:13:35 UTC 
[root@jetfire ~]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.65.201.71	jetfire		jetfire.lab.eng.pnq.redhat.com
[root@jetfire ~]# 

[root@jetfire ~]# ipa-server-install --setup-dns --no-forwarders --hostname=jetfire.lab.eng.pnq.redhat.com  -r LAB.ENG.PNQ.REDHAT.COM -n lab.eng.pnq.redhat.com -p Secret123 -P Secret123 -a Secret123 -U

The log file for this installation can be found in /var/log/ipaserver-install.log
==============================================================================
This program will set up the IPA Server.

This includes:
  * Configure a stand-alone CA (dogtag) for certificate management
  * Configure the Network Time Daemon (ntpd)
  * Create and configure an instance of Directory Server
  * Create and configure a Kerberos Key Distribution Center (KDC)
  * Configure Apache (httpd)
  * Configure DNS (bind)

To accept the default shown in brackets, press the Enter key.

The host name jetfire.lab.eng.pnq.redhat.com does not match the primary host name jetfire. Please check /etc/hosts or DNS name resolution

[root@jetfire ~]# 


Verified. Version: ipa-server-2.1.3-3.el6.x86_64
Comment 14 Martin Kosek 2011-11-01 07:49:10 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:
Cause: When IPA server is installed, it does not check properly system's static lookup table (/etc/hosts) for records that may interfere with its IP address or hostname.
Consequence: If /etc/hosts contains records with IP address or hostname matching the one configured for IPA, the IPA server installation may crash later during the installation process as forward or reverse DNS queries resolves to different values than expected.
Fix: ipa-server-install now always checks if there is a conflicting record in /etc/hosts and reports a clean error if there is any
Result: ipa-server-install won't crash because of conflicting records in /etc/hosts
Comment 15 errata-xmlrpc 2011-12-06 18:33:07 UTC 
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.

http://rhn.redhat.com/errata/RHSA-2011-1533.html
Comment 21 Red Hat Bugzilla 2023-11-08 04:25:03 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.