Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1447277[details]
/var/log/ipaserver-install.log
Description of problem:
Newest 7.6 bind build bind-9.9.4-65.el7 failed ipa-server-install at restarting named service
It was passing if I do a downgrade to bind-9.9.4-62.el7
.
.
.
01:31:12 [host-8-248-30.host.c] Configuring DNS (named)
01:31:12 [host-8-248-30.host.c] [1/12]: generating rndc key file
01:31:13 [host-8-248-30.host.c] [2/12]: adding DNS container
01:31:14 [host-8-248-30.host.c] [3/12]: setting up our zone
01:31:14 [host-8-248-30.host.c] [4/12]: setting up reverse zone
01:31:14 [host-8-248-30.host.c] [5/12]: setting up our own record
01:31:14 [host-8-248-30.host.c] [6/12]: setting up records for other masters
01:31:14 [host-8-248-30.host.c] [7/12]: adding NS record to the zones
01:31:14 [host-8-248-30.host.c] [8/12]: setting up kerberos principal
01:31:14 [host-8-248-30.host.c] [9/12]: setting up named.conf
01:31:14 [host-8-248-30.host.c] [10/12]: setting up server configuration
01:31:14 [host-8-248-30.host.c] [11/12]: configuring named to start on boot
01:31:14 [host-8-248-30.host.c] [12/12]: changing resolv.conf to point to ourselves
01:31:14 [host-8-248-30.host.c] Done configuring DNS (named).
01:31:17 [host-8-248-30.host.c] Restarting the web server to pick up resolv.conf changes
01:31:17 [host-8-248-30.host.c] Configuring DNS key synchronization service (ipa-dnskeysyncd)
01:31:17 [host-8-248-30.host.c] [1/7]: checking status
01:31:17 [host-8-248-30.host.c] [2/7]: setting up bind-dyndb-ldap working directory
01:31:17 [host-8-248-30.host.c] [3/7]: setting up kerberos principal
01:31:18 [host-8-248-30.host.c] [4/7]: setting up SoftHSM
01:31:18 [host-8-248-30.host.c] [5/7]: adding DNSSEC containers
01:31:18 [host-8-248-30.host.c] [6/7]: creating replica keys
01:31:19 [host-8-248-30.host.c] [7/7]: configuring ipa-dnskeysyncd to start on boot
01:31:19 [host-8-248-30.host.c] Done configuring DNS key synchronization service (ipa-dnskeysyncd).
01:31:19 [host-8-248-30.host.c] Restarting ipa-dnskeysyncd
01:31:19 [host-8-248-30.host.c] Restarting named
01:31:19 [host-8-248-30.host.c] ipa : ERROR Named service failed to start (Command '/bin/systemctl restart named-pkcs11.service' returned non-zero exit status 1)
01:31:19 [host-8-248-30.host.c] named service failed to start
01:31:19 [host-8-248-30.host.c] Updating DNS system records
01:31:28 [host-8-248-30.host.c] *** Current Time: Sun Jun 03 21:31:28 2018 Localwatchdog at: Mon Jun 04 00:20:28 2018
01:31:50 [host-8-248-30.host.c] ipa : ERROR DNS query for host-8-248-30.testrelm.test. 1 failed: The DNS operation timed out after 30.0016419888 seconds
01:31:55 [host-8-248-30.host.c] ipa : ERROR unable to resolve host name host-8-248-30.testrelm.test. to IP address, ipa-ca DNS record will be incomplete
01:31:55 [host-8-248-30.host.c] Configuring client side components
01:31:55 [host-8-248-30.host.c] Using existing certificate '/etc/ipa/ca.crt'.
01:31:55 [host-8-248-30.host.c] Client hostname: host-8-248-30.testrelm.test
01:31:55 [host-8-248-30.host.c] Realm: TESTRELM.TEST
01:31:55 [host-8-248-30.host.c] DNS Domain: testrelm.test
01:31:55 [host-8-248-30.host.c] IPA Server: host-8-248-30.testrelm.test
01:31:55 [host-8-248-30.host.c] BaseDN: dc=testrelm,dc=test
01:31:55 [host-8-248-30.host.c] Skipping synchronizing time with NTP server.
01:31:55 [host-8-248-30.host.c] New SSSD config will be created
01:31:55 [host-8-248-30.host.c] Configured sudoers in /etc/nsswitch.conf
01:31:55 [host-8-248-30.host.c] Configured /etc/sssd/sssd.conf
01:32:26 [host-8-248-30.host.c] trying https://host-8-248-30.testrelm.test/ipa/json
01:32:26 [host-8-248-30.host.c] [try 1]: Forwarding 'schema' to json server 'https://host-8-248-30.testrelm.test/ipa/json'
01:32:28 [host-8-248-30.host.c] *** Current Time: Sun Jun 03 21:32:28 2018 Localwatchdog at: Mon Jun 04 00:20:28 2018
01:32:57 [host-8-248-30.host.c] trying https://host-8-248-30.testrelm.test/ipa/session/json
01:32:57 [host-8-248-30.host.c] [try 1]: Forwarding 'ping' to json server 'https://host-8-248-30.testrelm.test/ipa/session/json'
01:32:57 [host-8-248-30.host.c] [try 1]: Forwarding 'ca_is_enabled' to json server 'https://host-8-248-30.testrelm.test/ipa/session/json'
01:32:59 [host-8-248-30.host.c] Systemwide CA database updated.
01:32:59 [host-8-248-30.host.c] Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
01:32:59 [host-8-248-30.host.c] Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
01:32:59 [host-8-248-30.host.c] Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
01:32:59 [host-8-248-30.host.c] [try 1]: Forwarding 'host_mod' to json server 'https://host-8-248-30.testrelm.test/ipa/session/json'
01:33:19 [host-8-248-30.host.c] Could not update DNS SSHFP records.
01:33:19 [host-8-248-30.host.c] SSSD enabled
01:33:20 [host-8-248-30.host.c] Configured /etc/openldap/ldap.conf
01:33:20 [host-8-248-30.host.c] Configured /etc/ssh/ssh_config
01:33:20 [host-8-248-30.host.c] Configured /etc/ssh/sshd_config
01:33:20 [host-8-248-30.host.c] Configuring testrelm.test as NIS domain.
01:33:20 [host-8-248-30.host.c] Client configuration complete.
01:33:20 [host-8-248-30.host.c] The ipa-client-install command was successful
01:33:25 [host-8-248-30.host.c] ipa.ipapython.install.cli.install_tool(CompatServerMasterInstall): ERROR Command '/bin/systemctl restart ipa.service' returned non-zero exit status 1
01:33:25 [host-8-248-30.host.c] ipa.ipapython.install.cli.install_tool(CompatServerMasterInstall): ERROR The ipa-server-install command failed. See /var/log/ipaserver-install.log for more information
Version-Release number of selected component (if applicable):
bind-9.9.4-65.el7
bind-dyndb-ldap-11.1-4.el7
ipa-server-4.5.4-10.el7_5.1
How reproducible:
Always
Steps to Reproduce:
1.Install ipa server
Actual results:
Install failed
Expected results:
Install pass
Additional info:
Attached ipaserver-install.log
With latest 7.6 ipa and bind builds,I had a successful server install.
# rpm -q bind bind-dyndb-ldap ipa-server
bind-9.9.4-67.el7.x86_64
bind-dyndb-ldap-11.1-4.el7.x86_64
ipa-server-4.6.4-1.el7.x86_64