Created attachment 480296 [details] /etc/hosts Description of problem: Version-Release number of selected component (if applicable): 2.0.0 Beta 2 RC1 How reproducible: 100% Steps to Reproduce: 1. Install Fedora 14 2. Install freeipa-server 3. Change hostname via /etc/sysconfig/network and reboot 4. Attempt to run ipa-server-install 5. Accept server host name default value Actual results: Server host name [dc01.example.com]: Unexpected error - see ipaserver-install.log for details: The IPA Server hostname cannot resolve to localhost (::1). A routable IP address must be used. Check /etc/hosts to see if dc01.example.com is an alias for ::1 Expected results: ipa server setup executes Additional info: ipaserver-install.log was not created in the directory where the ipa-server-install command was executed (/home/jar349), so unless it goes somewhere specific, it was not created.
This is correct behavior. As the error explains, you cannot install IPA if the hostname resolves to either the IPv4 or IPv6 localhost address (127.0.0.1 and ::1). NetworkManager is infamous for modifying /etc/hosts, see BZ 648725. To fix this add an entry for your hostname and IP address to /etc/hosts. Make sure the FQDN appears first: 192.168.0.1 dc01.example.com dc01 Possible solutions include: - update NetworkManager when it becomes available - install nss-myhostname - uninstall NetworkManager and use the old network init service ipaserver-install.log is in /var/log
If that is correct behavior then this is still a bug - just for a different reason. The sentence "The IPA Server hostname cannot resolve to localhost" should instead be "The IPA Server hostname must not resolve to localhost" The word "Can" denotes ability whereas "may" denotes permission. Currently, the error says "I do not have the ability to resolve to localhost", which implies that it requires the ability - which is why I configured my hosts file as I did. see: http://www.businesswritingblog.com/business_writing/2006/08/can_vs_maynot_s.html
https://fedorahosted.org/freeipa/ticket/1009
Thank you. Closing this bug.