Likely related tickets:

https://fedorahosted.org/freeipa/ticket/2648
https://fedorahosted.org/freeipa/ticket/2715

Fix is potentially in:

https://fedorahosted.org/freeipa/ticket/4317

(In reply to Jan Pazdziora from comment #1)
> 
> Fix is potentially in:
> 
> https://fedorahosted.org/freeipa/ticket/4317

Pasted wrong link -- fix is potentially in:

https://fedorahosted.org/freeipa/ticket/5814

I'd say that this is more bugfix of missing validation in 7.2 and not regression in 7.3. AFAIK is intended for all installers to check if local address match resolved addresses (at least without DNS installation) to prevent IP misconfiguration on local or DNS side

Ticket #5814 allows to use network/broadcast addresses, but there is still need to ip-address on a local interface


Related tickets for this: #4317, #2715

Seeing get_server_ip_address has special check for ['127.0.0.1', '::1'], I've also tried to use --ip-address=127.0.0.2 to force local address yet one which is not in the list but that fails with

ipa-server-install: error: option --ip-address: invalid IP address 127.0.0.2: cannot use loopback IP address 127.0.0.2

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4317

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2715

Quick workaround:

diff --git a/ipaserver/install/installutils.py b/ipaserver/install/installutils.py
index 7578bf8..211f6f2 100644
--- a/ipaserver/install/installutils.py
+++ b/ipaserver/install/installutils.py
@@ -508,7 +508,7 @@ def get_server_ip_address(host_name, unattended, setup_dns, ip_addresses):
     if len(hostaddr):
         for ha in hostaddr:
             try:
-                ips.append(ipautil.CheckedIPAddress(ha, match_local=True))
+                ips.append(ipautil.CheckedIPAddress(ha, match_local=False))
             except ValueError as e:
                 root_logger.warning("Invalid IP address %s for %s: %s", ha, host_name, unicode(e))

(In reply to Jan Pazdziora from comment #5)
> Seeing get_server_ip_address has special check for ['127.0.0.1', '::1'],
> I've also tried to use --ip-address=127.0.0.2 to force local address yet one
> which is not in the list but that fails with
> 
> ipa-server-install: error: option --ip-address: invalid IP address
> 127.0.0.2: cannot use loopback IP address 127.0.0.2

There is ticket for loopback addresses to be allowed in --forwarder option
https://fedorahosted.org/freeipa/ticket/5801

However I don't see reason why loopback addresses should be allowed as address of IPA server.

Perhaps because in certain environments like in containers, the loopback addresses are the only thing that you can reliably assume to be available with certain value before starting the environment.

Since IPA is now able to update its own IP address in the DNS post-installation, why does the installer even care that loopback IP address is used during installation? Especially when specified explicitly by the admin, not merely autodiscovered by the installer.

Ok, I don't know what can breaks in IPA using loopback address, please file a separate ticket to allow usage of loopback address.

Ideally, the check in installer which tries to figure out if the IP address is IPA server's IP address, wouldn't try to look at its network interfaces but would instead (or in addition) try to use that IP address (make request on port 443 or similar) and check that it is routed back to the IPA server. That would cover both the NAT use cases of AWS and the port exposure of containers.

(In reply to Martin Bašti from comment #11)
> Ok, I don't know what can breaks in IPA using loopback address, please file
> a separate ticket to allow usage of loopback address.

For me the use of loopback addresses is not essential -- I've merely showed is as an example of approaches that I've tried as workaround.

Fixed upstream:
master:
https://pagure.io/freeipa/c/6637980af6069623d944d9d592cbadba20b610a2
ipa-4-5:
https://pagure.io/freeipa/c/6206ac8bd23250bda0f8eb628f422671b9b99ad1

Besed on above observations in comment#28 and comment#29, changing the status of bug to "ASSIGNED"

Fixed upstream
master:
https://pagure.io/freeipa/c/82ad586f6cbf6e707add3c866ed4e37ade69b045
https://pagure.io/freeipa/c/cb48a49c80f4a11d2d16511e0f1366867320f153
https://pagure.io/freeipa/c/0b69e44f16fbba6ab7ddef5a3e55bdabcfd6a8a6
https://pagure.io/freeipa/c/6024165101677c844dc3bbb337e290df2e66eaf1
https://pagure.io/freeipa/c/f9cba7d161f788c32336b66ff7c641f4a1ed2754
https://pagure.io/freeipa/c/1b8dc1131c9ca7218efb8fe16dcce97f9f960be9
https://pagure.io/freeipa/c/f3537297bee2890c6b839750bb7a0a2cf904cdf9

Fixed upstream
ipa-4-5:
https://pagure.io/freeipa/c/d010191d170c0ebb5f46bac2fc528f788e8ffc41
https://pagure.io/freeipa/c/4d06f0c52200a4345db36dae3fdbc178f18f2f01
https://pagure.io/freeipa/c/0aa0041149f359f1954409baf886d4b31fdadc16
https://pagure.io/freeipa/c/9a924dd8cc27507a70f4ec5020d97417e149e350
https://pagure.io/freeipa/c/217905a20071b55b50568e8fbb36a8ecde974432
https://pagure.io/freeipa/c/93ef10292ca674842c79da0dab6de6fb63261881
https://pagure.io/freeipa/c/1c961161873c37cb29a51baeeed0e782cd4a1d4d

ipa-server: ipa-server-4.5.0-19.el7.x86_64

Verified the bug on the basis of following observations:
1. Verified that IPA-server installation is successful and no Warning messages are displayed when there is valid/correct IP address is associated with network interface and also host name is correctly resolvable.
2. Verified that no such warning message is displayed during replica-installation as well.

Console:
------------- 
[root@auto-hv-01-guest06 ~]# hostname
auto-hv-01-guest06.testrelm.test
[root@auto-hv-01-guest06 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 52:54:00:13:e7:2d brd ff:ff:ff:ff:ff:ff
    inet 10.x.x.x/23 brd 10.19.35.255 scope global dynamic eth0
       valid_lft 85931sec preferred_lft 85931sec
    inet6 2620:52:0:1322:5054:ff:fe13:e72d/64 scope global noprefixroute dynamic
       valid_lft 2591811sec preferred_lft 604611sec
    inet6 fe80::5054:ff:fe13:e72d/64 scope link
       valid_lft forever preferred_lft forever
[root@auto-hv-01-guest06 ~]# rpm -q ipa-server
ipa-server-4.5.0-19.el7.x86_64
[root@auto-hv-01-guest06 ~]# ipa-server-install
 
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 the KDC to enable PKINIT
 
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 [auto-hv-01-guest06.testrelm.test]:
 
Warning: skipping DNS resolution of host auto-hv-01-guest06.testrelm.test
The domain name has been determined based on the host name.
 
Please confirm the domain name [testrelm.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 [TESTRELM.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):
 
Checking DNS domain testrelm.test., please wait ...
Do you want to configure DNS forwarders? [yes]:
Following DNS servers are configured in /etc/resolv.conf: 10.x.x.x
Do you want to configure these servers as DNS forwarders? [yes]:
All DNS servers from /etc/resolv.conf were added. You can enter additional addresses now:
Enter an IP address for a DNS forwarder, or press Enter to skip: 10.x.x.x
DNS forwarder 10.x.x.x added. You may add another.
Enter an IP address for a DNS forwarder, or press Enter to skip:
Checking DNS forwarders, please wait ...
Do you want to search for missing reverse zones? [yes]:
 
The IPA Master Server will be configured with:
Hostname:       auto-hv-01-guest06.testrelm.test
IP address(es): 10.x.x.x
Domain name:    testrelm.test
Realm name:     TESTRELM.TEST
 
BIND DNS server will be configured to serve IPA domain with:
Forwarders:       10.x.x.x, 10.x.x.x
Forward policy:   only
Reverse zone(s):  No reverse zone
 
Continue to configure the system with these values? [no]: yes
 
The following operations may take some minutes to complete.
Please wait until the prompt is returned.
 
Configuring NTP daemon (ntpd)
  [1/4]: stopping ntpd
  [2/4]: writing configuration
  [3/4]: configuring ntpd to start on boot
  [4/4]: starting ntpd
Done configuring NTP daemon (ntpd).
Configuring directory server (dirsrv). Estimated time: 30 seconds
  [1/45]: creating directory server instance
  [2/45]: enabling ldapi
  [3/45]: configure autobind for root
  [4/45]: stopping directory server
  [5/45]: updating configuration in dse.ldif
  [6/45]: starting directory server
  [7/45]: adding default schema
  [8/45]: enabling memberof plugin
  [9/45]: enabling winsync plugin
  [10/45]: configuring replication version plugin
  [11/45]: enabling IPA enrollment plugin
  [12/45]: configuring uniqueness plugin
  [13/45]: configuring uuid plugin
  [14/45]: configuring modrdn plugin
  [15/45]: configuring DNS plugin
  [16/45]: enabling entryUSN plugin
  [17/45]: configuring lockout plugin
  [18/45]: configuring topology plugin
  [19/45]: creating indices
  [20/45]: enabling referential integrity plugin
  [21/45]: configuring certmap.conf
  [22/45]: configure new location for managed entries
  [23/45]: configure dirsrv ccache
  [24/45]: enabling SASL mapping fallback
  [25/45]: restarting directory server
  [26/45]: adding sasl mappings to the directory
  [27/45]: adding default layout
  [28/45]: adding delegation layout
  [29/45]: creating container for managed entries
  [30/45]: configuring user private groups
  [31/45]: configuring netgroups from hostgroups
  [32/45]: creating default Sudo bind user
  [33/45]: creating default Auto Member layout
  [34/45]: adding range check plugin
  [35/45]: creating default HBAC rule allow_all
  [36/45]: adding entries for topology management
  [37/45]: initializing group membership
  [38/45]: adding master entry
  [39/45]: initializing domain level
  [40/45]: configuring Posix uid/gid generation
  [41/45]: adding replication acis
  [42/45]: activating sidgen plugin
  [43/45]: activating extdom plugin
  [44/45]: tuning directory server
  [45/45]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring Kerberos KDC (krb5kdc)
  [1/10]: adding kerberos container to the directory
  [2/10]: configuring KDC
  [3/10]: initialize kerberos container
  [4/10]: adding default ACIs
  [5/10]: creating a keytab for the directory
  [6/10]: creating a keytab for the machine
  [7/10]: adding the password extension to the directory
  [8/10]: creating anonymous principal
  [9/10]: starting the KDC
  [10/10]: configuring KDC to start on boot
Done configuring Kerberos KDC (krb5kdc).
Configuring kadmin
  [1/2]: starting kadmin
  [2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes
  [1/29]: configuring certificate server instance
  [2/29]: exporting Dogtag certificate store pin
  [3/29]: stopping certificate server instance to update CS.cfg
  [4/29]: backing up CS.cfg
  [5/29]: disabling nonces
  [6/29]: set up CRL publishing
  [7/29]: enable PKIX certificate path discovery and validation
  [8/29]: starting certificate server instance
  [9/29]: configure certmonger for renewals
  [10/29]: requesting RA certificate from CA
  [11/29]: setting up signing cert profile
  [12/29]: setting audit signing renewal to 2 years
  [13/29]: restarting certificate server
  [14/29]: publishing the CA certificate
  [15/29]: adding RA agent as a trusted user
  [16/29]: authorizing RA to modify profiles
  [17/29]: authorizing RA to manage lightweight CAs
  [18/29]: Ensure lightweight CAs container exists
  [19/29]: configure certificate renewals
  [20/29]: configure Server-Cert certificate renewal
  [21/29]: Configure HTTP to proxy connections
  [22/29]: restarting certificate server
  [23/29]: updating IPA configuration
  [24/29]: enabling CA instance
  [25/29]: migrating certificate profiles to LDAP
  [26/29]: importing IPA certificate profiles
  [27/29]: adding default CA ACL
  [28/29]: adding 'ipa' CA entry
  [29/29]: configuring certmonger renewal for lightweight CAs
Done configuring certificate server (pki-tomcatd).
Configuring directory server (dirsrv)
  [1/3]: configuring TLS for DS instance
  [2/3]: adding CA certificate entry
  [3/3]: restarting directory server
Done configuring directory server (dirsrv).
Configuring ipa-otpd
  [1/2]: starting ipa-otpd
  [2/2]: configuring ipa-otpd to start on boot
Done configuring ipa-otpd.
Configuring ipa-custodia
  [1/5]: Generating ipa-custodia config file
  [2/5]: Making sure custodia container exists
  [3/5]: Generating ipa-custodia keys
  [4/5]: starting ipa-custodia
  [5/5]: configuring ipa-custodia to start on boot
Done configuring ipa-custodia.
Configuring the web interface (httpd)
  [1/22]: stopping httpd
  [2/22]: setting mod_nss port to 443
  [3/22]: setting mod_nss cipher suite
  [4/22]: setting mod_nss protocol list to TLSv1.0 - TLSv1.2
  [5/22]: setting mod_nss password file
  [6/22]: enabling mod_nss renegotiate
  [7/22]: disabling mod_nss OCSP
  [8/22]: adding URL rewriting rules
  [9/22]: configuring httpd
  [10/22]: setting up httpd keytab
  [11/22]: configuring Gssproxy
  [12/22]: setting up ssl
  [13/22]: configure certmonger for renewals
  [14/22]: importing CA certificates from LDAP
  [15/22]: publish CA cert
  [16/22]: clean up any existing httpd ccaches
  [17/22]: configuring SELinux for httpd
  [18/22]: create KDC proxy config
  [19/22]: enable KDC proxy
  [20/22]: starting httpd
  [21/22]: configuring httpd to start on boot
  [22/22]: enabling oddjobd
Done configuring the web interface (httpd).
Configuring Kerberos KDC (krb5kdc)
  [1/1]: installing X509 Certificate for PKINIT
Done configuring Kerberos KDC (krb5kdc).
Applying LDAP updates
Upgrading IPA:. Estimated time: 1 minute 30 seconds
  [1/9]: stopping directory server
  [2/9]: saving configuration
  [3/9]: disabling listeners
  [4/9]: enabling DS global lock
  [5/9]: starting directory server
  [6/9]: upgrading server
  [7/9]: stopping directory server
  [8/9]: restoring configuration
  [9/9]: starting directory server
Done.
Restarting the KDC
Configuring DNS (named)
  [1/11]: generating rndc key file
  [2/11]: adding DNS container
  [3/11]: setting up our zone
  [4/11]: setting up our own record
  [5/11]: setting up records for other masters
  [6/11]: adding NS record to the zones
  [7/11]: setting up kerberos principal
  [8/11]: setting up named.conf
  [9/11]: setting up server configuration
  [10/11]: configuring named to start on boot
  [11/11]: changing resolv.conf to point to ourselves
Done configuring DNS (named).
Restarting the web server to pick up resolv.conf changes
Configuring DNS key synchronization service (ipa-dnskeysyncd)
  [1/7]: checking status
  [2/7]: setting up bind-dyndb-ldap working directory
  [3/7]: setting up kerberos principal
  [4/7]: setting up SoftHSM
  [5/7]: adding DNSSEC containers
  [6/7]: creating replica keys
  [7/7]: configuring ipa-dnskeysyncd to start on boot
Done configuring DNS key synchronization service (ipa-dnskeysyncd).
Restarting ipa-dnskeysyncd
Restarting named
Updating DNS system records
Configuring client side components
Using existing certificate '/etc/ipa/ca.crt'.
Client hostname: auto-hv-01-guest06.testrelm.test
Realm: TESTRELM.TEST
DNS Domain: testrelm.test
IPA Server: auto-hv-01-guest06.testrelm.test
BaseDN: dc=testrelm,dc=test
 
Skipping synchronizing time with NTP server.
New SSSD config will be created
Configured sudoers in /etc/nsswitch.conf
Configured /etc/sssd/sssd.conf
trying https://auto-hv-01-guest06.testrelm.test/ipa/json
[try 1]: Forwarding 'schema' to json server 'https://auto-hv-01-guest06.testrelm.test/ipa/json'
trying https://auto-hv-01-guest06.testrelm.test/ipa/session/json
[try 1]: Forwarding 'ping' to json server 'https://auto-hv-01-guest06.testrelm.test/ipa/session/json'
[try 1]: Forwarding 'ca_is_enabled' to json server 'https://auto-hv-01-guest06.testrelm.test/ipa/session/json'
Systemwide CA database updated.
Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
[try 1]: Forwarding 'host_mod' to json server 'https://auto-hv-01-guest06.testrelm.test/ipa/session/json'
SSSD enabled
Configured /etc/openldap/ldap.conf
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Configuring testrelm.test as NIS domain.
Client configuration complete.
The ipa-client-install command was successful
 
==============================================================================
Setup complete
 
Next steps:
        1. You must make sure these network ports are open:
                TCP Ports:
                  * 80, 443: HTTP/HTTPS
                  * 389, 636: LDAP/LDAPS
                  * 88, 464: kerberos
                  * 53: bind
                UDP Ports:
                  * 88, 464: kerberos
                  * 53: bind
                  * 123: ntp
 
        2. You can now obtain a kerberos ticket using the command: 'kinit admin'
           This ticket will allow you to use the IPA tools (e.g., ipa user-add)
           and the web user interface.
 
Be sure to back up the CA certificates stored in /root/cacert.p12
These files are required to create replicas. The password for these
files is the Directory Manager password
[root@auto-hv-01-guest06 ~]#

Thus on the basis of above observations, marking status of bug to "VERIFIED".

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.

https://access.redhat.com/errata/RHBA-2017:2304