Bug 1436623
| Summary: | ipa-server-install stuck on Updating DNS system records | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Varun Mylaraiah <mvarun> | ||||||||
| Component: | ipa | Assignee: | Tomas Krizek <tkrizek> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | ipa-qe <ipa-qe> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 7.4 | CC: | mbasti, mvarun, pvoborni, rcritten, tbordaz, tkrizek, tscherf | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-04-20 15:13:01 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1266903 [details]
httpd error log
Created attachment 1266905 [details]
389ds log
can you please provide ipaserver-install.log? (In reply to Martin Bašti from comment #4) > can you please provide ipaserver-install.log? Already Attached Oh sorry I missed that. It stucked in the middle of cycle which is SRV adding records to LDAP and given many errors in LDAP error log I assume it is waiting for LDAP operations. Thierry can you please check what the errors in DS log means and if they can cause unresponsive LDAP operations? The warnings in DS log are related to nunc stans bug that caused bind-dyndb-ldap to misbehave. The nunc stans bug 1432149 is fixed since 389-ds-base-1.3.6.1-2.el7. It might be the cause of this bug as well. Varun, can you please upgrade 389-ds-base to a version that has the above bug fixed and check whether this issue is still present? (In reply to Tomas Krizek from comment #7) > The warnings in DS log are related to nunc stans bug that caused > bind-dyndb-ldap to misbehave. The nunc stans bug 1432149 is fixed since > 389-ds-base-1.3.6.1-2.el7. > > It might be the cause of this bug as well. > > Varun, can you please upgrade 389-ds-base to a version that has the above > bug fixed and check whether this issue is still present? Installation failing with latest 389-ds. Please have a look bug 1438724 Seems to me that in bug 1438724 it actually went past this issue and failed on something else which looked more related to DNS config. in 389-ds logs: - connection timeout messages are related to https://bugzilla.redhat.com/show_bug.cgi?id=1404409 fixed in 389-ds-base-1.3.6.2-2.f26 - cos messages are related to https://bugzilla.redhat.com/show_bug.cgi?id=1437492 no yet fixed Would be good to retest this bug with 389-ds-base-1.3.6.1-7.el7 (bug 1394899 resp. bug 1438724) and close if it works. Comment 7 says it the crash was due to bug 1432149. After retesting with the version which has a fix for the bug, it fails further in the process with bug 1438724. Therefore closing as dup of 1432149 *** This bug has been marked as a duplicate of bug 1432149 *** |
Created attachment 1266902 [details] ipa-server-install log Description of problem: ipa-server-install stuck on Updating DNS system records Version-Release number of selected component (if applicable): ipa-server-4.5.0-2.el7.x86_64 Steps to Reproduce: [root@bkr-hv03-guest33 ~]# getenforce Permissive [root@bkr-hv03-guest33 ~]# ipa-server-install --setup-dns --forwarder=10.16.36.29 --reverse-zone=41.19.10.in-addr.arpa. --allow-zone-overlap --hostname=bkr-hv03-guest33.testrelmasdf.test -r TESTRELMASDF.TEST -n testrelmasdf.test. -p Secret123 -a Secret123 --ip-address=10.19.41.63 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) * 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 Warning: skipping DNS resolution of host bkr-hv03-guest33.testrelmasdf.test Checking DNS domain testrelmasdf.test., please wait ... Checking DNS forwarders, please wait ... Using reverse zone(s) 41.19.10.in-addr.arpa. The IPA Master Server will be configured with: Hostname: bkr-hv03-guest33.testrelmasdf.test IP address(es): 10.19.41.63 Domain name: testrelmasdf.test. Realm name: TESTRELMASDF.TEST BIND DNS server will be configured to serve IPA domain with: Forwarders: 10.16.36.29 Forward policy: only Reverse zone(s): 41.19.10.in-addr.arpa. WARNING: Realm name does not match the domain name. You will not be able to estabilish trusts with Active Directory unless the realm name of the IPA server matches its domain name. 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. Adding [10.19.41.63 bkr-hv03-guest33.testrelmasdf.test] to your /etc/hosts file 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/47]: creating directory server user [2/47]: creating directory server instance [3/47]: enabling ldapi [4/47]: configure autobind for root [5/47]: stopping directory server [6/47]: updating configuration in dse.ldif [7/47]: starting directory server [8/47]: adding default schema [9/47]: enabling memberof plugin [10/47]: enabling winsync plugin [11/47]: configuring replication version plugin [12/47]: enabling IPA enrollment plugin [13/47]: configuring uniqueness plugin [14/47]: configuring uuid plugin [15/47]: configuring modrdn plugin [16/47]: configuring DNS plugin [17/47]: enabling entryUSN plugin [18/47]: configuring lockout plugin [19/47]: configuring topology plugin [20/47]: creating indices [21/47]: enabling referential integrity plugin [22/47]: configuring certmap.conf [23/47]: configure new location for managed entries [24/47]: configure dirsrv ccache [25/47]: enabling SASL mapping fallback [26/47]: restarting directory server [27/47]: adding sasl mappings to the directory [28/47]: adding default layout [29/47]: adding delegation layout [30/47]: creating container for managed entries [31/47]: configuring user private groups [32/47]: configuring netgroups from hostgroups [33/47]: creating default Sudo bind user [34/47]: creating default Auto Member layout [35/47]: adding range check plugin [36/47]: creating default HBAC rule allow_all [37/47]: adding entries for topology management [38/47]: initializing group membership [39/47]: adding master entry [40/47]: initializing domain level [41/47]: configuring Posix uid/gid generation [42/47]: adding replication acis [43/47]: enabling compatibility plugin [44/47]: activating sidgen plugin [45/47]: activating extdom plugin [46/47]: tuning directory server [47/47]: configuring directory to start on boot Done configuring directory server (dirsrv). Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes [1/30]: creating certificate server user [2/30]: configuring certificate server instance [3/30]: exporting Dogtag certificate store pin [4/30]: stopping certificate server instance to update CS.cfg [5/30]: backing up CS.cfg [6/30]: disabling nonces [7/30]: set up CRL publishing [8/30]: enable PKIX certificate path discovery and validation [9/30]: starting certificate server instance [10/30]: configure certmonger for renewals [11/30]: requesting RA certificate from CA [12/30]: setting up signing cert profile [13/30]: setting audit signing renewal to 2 years [14/30]: restarting certificate server [15/30]: publishing the CA certificate [16/30]: adding RA agent as a trusted user [17/30]: authorizing RA to modify profiles [18/30]: authorizing RA to manage lightweight CAs [19/30]: Ensure lightweight CAs container exists [20/30]: configure certificate renewals [21/30]: configure Server-Cert certificate renewal [22/30]: Configure HTTP to proxy connections [23/30]: restarting certificate server [24/30]: migrating certificate profiles to LDAP [25/30]: importing IPA certificate profiles [26/30]: adding default CA ACL [27/30]: adding 'ipa' CA entry [28/30]: updating IPA configuration [29/30]: enabling CA instance [30/30]: 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]: restarting directory server [3/3]: adding CA certificate entry 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 WARNING: Your system is running out of entropy, you may experience long delays [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. Restarting directory server to enable password extension plugin 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]: setting mod_nss port to 443 [2/22]: setting mod_nss cipher suite [3/22]: setting mod_nss protocol list to TLSv1.0 - TLSv1.2 [4/22]: setting mod_nss password file [5/22]: enabling mod_nss renegotiate [6/22]: adding URL rewriting rules [7/22]: configuring httpd [8/22]: setting up httpd keytab [9/22]: retrieving anonymous keytab [10/22]: configuring Gssproxy [11/22]: setting up ssl [12/22]: configure certmonger for renewals [13/22]: importing CA certificates from LDAP [14/22]: publish CA cert [15/22]: clean up any existing httpd ccaches [16/22]: configuring SELinux for httpd [17/22]: create KDC proxy user [18/22]: create KDC proxy config [19/22]: enable KDC proxy [20/22]: restarting 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/12]: generating rndc key file WARNING: Your system is running out of entropy, you may experience long delays [2/12]: adding DNS container [3/12]: setting up our zone [4/12]: setting up reverse zone [5/12]: setting up our own record [6/12]: setting up records for other masters [7/12]: adding NS record to the zones [8/12]: setting up kerberos principal [9/12]: setting up named.conf [10/12]: setting up server configuration [11/12]: configuring named to start on boot [12/12]: 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 Actual results: IPA install fails Expected results: IPA install should be successful Additional info: 1) selinux is in permissive mode 2) Please find the attached ds error log file 3) ipa and ds Versions ipa-server-common-4.5.0-2.el7.noarch ipa-client-4.5.0-2.el7.x86_64 ipa-server-dns-4.5.0-2.el7.noarch ipa-common-4.5.0-2.el7.noarch ipa-client-common-4.5.0-2.el7.noarch ipa-server-4.5.0-2.el7.x86_64 389-ds-base-libs-1.3.6.1-4.el7.x86_64 389-ds-base-1.3.6.1-4.el7.x86_64