#6222 [RFE] improve make install to handle platform specifics
Closed: invalid by rcritten. Opened by jhh.

ipa-server-install

The log file for this installation can be found in /var/log/ipaserver-install.log
==============================================================================
This program will set up the FreeIPA 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)
To accept the default shown in brackets, press the Enter key.
WARNING: conflicting time&date synchronization service 'chronyd' will be disabled
in favor of ntpd
Do you want to configure integrated DNS (BIND)? [no]: yes
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
<hostname>.<domainname>
Example: master.example.com.
Server host name [ipa.example.com]:
Warning: skipping DNS resolution of host ipa.example.com
The domain name has been determined based on the host name.
Please confirm the domain name [example.com]: example.test
The kerberos protocol requires a Realm name to be defined.
This is typically the domain name converted to uppercase.
Please provide a realm name [EXAMPLE.TEST]: 
Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and has full access
to the Directory for system management tasks and will be added to the
instance of directory server created for IPA.
The password must be at least 8 characters long.
Directory Manager password: 
Password (confirm):
The IPA server requires an administrative user, named 'admin'.
This user is a regular system account used for IPA server administration.
IPA admin password: 
Password (confirm):
ipa.ipapython.install.cli.install_tool(Server): ERROR    Integrated DNS requires 'ipa-server-dns' package

Seems like normal, expected behavior - not a bug.

Based on the error message on the end of command output it seems that ipa-server-dns package is not installed.

I suggest to install the rpm package.

I'm using the 4.4.0 tarball and there doesn't seem to be anything else to download.
Where does this package live and why would it not be in the tarball?

So how exactly do you install IPA? What OS do you use?

I went to your site, downloaded the 4.4.0 tar ball from downloads, expanded it and ran the installer on a fresh install of RHEL 7.2.

After googling around it seems the tar ball has been broke for a while.

So I tried the 4.2.x version that is packaged with RHEL. It looks like some one at RHEL fixed that issue but slightly broke the kerberos setup. I had to uninstall and manually edit /etc/krb5.conf before it would finally complete.

Not getting warm fuzzies.

Current IPA build system doesn't support direct installation using make install independently on OS much. Atm it is mostly useful only for building rpm packages with rpm spec file suited for certain OSes. E.g. the upstream rpm spec file is mostly useful for recent Fedoras.

Os specific part of FreeIPA are handled in so called "platform" files. The error message about is one of such occurrences. Basically it means that it expects that IPA will be installed from RPM packages.

Additionally FreeIPA 4.4 doesn't work on RHEL 7.2 out of the box. It depends on several components which are not part of 7.2.

Given these reasons I'd close this bug as invalid. But an RFE to support make install directly may be a valid one but in that case, I'd suggest to open a new one with attached use case.

If it doesn't support it, don't distribute it as if it does. Pretty simple.

If you think an RFE is indicated - open one.

Not my monkey.

FreeIPA web pages don't advertise make install anywhere as far as I know. The procedure exists and tarball is released because they are needed for building Fedora, RHEL and Debian packages.

It is recommended to use downstream packages when they are ready.

Metadata Update from @jhh:
- Issue assigned to someone
- Issue set to the milestone: Future Releases

Metadata Update from @rcritten:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

Metadata