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.
Bug 1440232 - ipa-kra-install on replica failed: Error: Incorrect client security database password.
Summary: ipa-kra-install on replica failed: Error: Incorrect client security database ...
Keywords:
Status: CLOSED DUPLICATE of bug 1438679
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-07 15:45 UTC by Martin Bašti
Modified: 2017-04-13 15:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-13 15:56:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Bašti 2017-04-07 15:45:15 UTC 
Description of problem:
ipa-kra-install command failed

ipa KRA install log:
2017-04-07T15:12:41Z DEBUG Starting external process
2017-04-07T15:12:41Z DEBUG args=/usr/sbin/pkispawn -s KRA -f /tmp/tmp9SX5Dv
2017-04-07T15:12:43Z DEBUG Process finished, return code=1
2017-04-07T15:12:43Z DEBUG stdout=Log file: /var/log/pki/pki-kra-spawn.20170407171242.log
Loading deployment configuration from /tmp/tmp9SX5Dv.
Installing KRA into /var/lib/pki/pki-tomcat.
Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-tomcat/kra/deployment.cfg.
Importing certificates from /tmp/tmpKtiUUq:

Installation failed: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-C', '/etc/pki/pki-tomcat/pfile', 'pkcs12-cert-find', '--pkcs12-file', '/tmp/tmpKtiUUq', '--pkcs12-password-file', '/tmp/tmpc3DiEM/passwo
rd.txt']' returned non-zero exit status 255


2017-04-07T15:12:43Z DEBUG stderr=Error: Incorrect client security database password.

2017-04-07T15:12:43Z CRITICAL Failed to configure KRA instance: Command '/usr/sbin/pkispawn -s KRA -f /tmp/tmp9SX5Dv' returned non-zero exit status 1
2017-04-07T15:12:43Z CRITICAL See the installation logs and the following files/directories for more information:
2017-04-07T15:12:43Z CRITICAL   /var/log/pki/pki-tomcat
2017-04-07T15:12:43Z DEBUG Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/ipaserver/install/service.py", line 423, in start_creation
    run_step(full_msg, method)
  File "/usr/lib/python2.7/site-packages/ipaserver/install/service.py", line 413, in run_step
    method()
  File "/usr/lib/python2.7/site-packages/ipaserver/install/krainstance.py", line 282, in __spawn_instance
    nolog_list=(self.dm_password, self.admin_password, pki_pin)
  File "/usr/lib/python2.7/site-packages/ipaserver/install/dogtaginstance.py", line 148, in spawn_instance
    self.handle_setup_error(e)
  File "/usr/lib/python2.7/site-packages/ipaserver/install/dogtaginstance.py", line 395, in handle_setup_error
    raise RuntimeError("%s configuration failed." % self.subsystem)
RuntimeError: KRA configuration failed.


pki-kra-spawn.log
2017-04-07 17:12:43 pkispawn    : DEBUG    ....... Error Type: CalledProcessError
2017-04-07 17:12:43 pkispawn    : DEBUG    ....... Error Message: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-C', '/etc/pki/pki-tomcat/pfile', 'pkcs12-cert-find', '--pkcs12-file', '/tmp/tmpKtiUUq', '--pkcs12-password-file', '/tmp/tmpc3DiEM/password.txt']' returned non-zero exit status 255
2017-04-07 17:12:43 pkispawn    : DEBUG    .......   File "/usr/sbin/pkispawn", line 500, in main
    scriptlet.spawn(deployer)
  File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/security_databases.py", line 146, in spawn
    pkcs12.show_certs()
  File "/usr/lib/python2.7/site-packages/pki/pkcs12.py", line 73, in show_certs
    subprocess.check_call(cmd)
  File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call
    raise CalledProcessError(retcode, cmd)

Because I see upstream KRA tests green, I assume this is broken only in RHEL.

selinux is in permissive mode

Version-Release number of selected component (if applicable):
ipa-server-4.5.0-4.el7.x86_64
pki-kra-10.4.1-1.el7.noarch


How reproducible:
Always

Steps to Reproduce:
1. ipa-server-install --setup-kra
2. ipa-replica-install
3. ipa-kra-install (on replica)

Actual results:
KRA installation failed

Expected results:
KRA to be installed

Additional info:
Comment 2 Petr Vobornik 2017-04-07 17:39:09 UTC 
Might be bug 1438679
Comment 3 Petr Vobornik 2017-04-13 15:56:02 UTC 

*** This bug has been marked as a duplicate of bug 1438679 ***
Note You need to log in before you can comment on or make changes to this bug.