Bug 447440 - /etc/hosts and ipa* problems
Summary: /etc/hosts and ipa* problems
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: freeIPA
Classification: Retired
Component: Documentation
Version: 1.0
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: David O'Brien
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: 429034
TreeView+ depends on / blocked
 
Reported: 2008-05-19 21:47 UTC by Mark Christiansen
Modified: 2015-01-04 23:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-12 04:39:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Mark Christiansen 2008-05-19 21:47:51 UTC
Description of problem:

Installation with localhost as the first entry in /etc/hosts presents problems
with ipa* commands.  Moving the FQDN to the first entry and the localhost entry
down fixes this problem.

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

v1.0 - could apply to other branches

How reproducible:

Install with localhost as first entry in /etc/hosts

Steps to Reproduce:
1. "yum install" method
2.
3.
  
Actual results:

Uing kinit and klist works, but ipa* commands give an error with GSSAPI.

Expected results:

ipa* should not give an error back

Additional info:

Modifying /etc/hosts to have FQDN fixes ipa* problems.  Documentation should
reflect this, or the installation process should move these files around for the
end user.

Comment 1 David O'Brien 2008-05-20 02:36:37 UTC
Add to both Installation Guide and Troubleshooting.

Comment 4 David O'Brien 2008-05-22 15:48:56 UTC
Added sub-section 2.4. Configuring the /etc/hosts File to the "Preparing for an
IPA Installation" chapter in the Installation and Deployment Guide.

Comment 5 Yi Zhang 2008-05-23 16:02:44 UTC
QA Verified on May 23, 2008 (Yi)

Build used: May 23, 2008 (x64)



Comment 6 Yi Zhang 2008-05-23 16:03:14 UTC
the document is here
http://www.freeipa.com/page/InstallAndDeploy#Configuring_.2Fetc.2Fhosts


Note You need to log in before you can comment on or make changes to this bug.