Bug 1984431 - Two-step KRA installation with external certificates fails on Non-HSM & HSM system
Summary: Two-step KRA installation with external certificates fails on Non-HSM & HSM s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Certificate System
Classification: Red Hat
Component: pki-core
Version: 10.3
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ---
: certsys-10.3
Assignee: Christina Fu
QA Contact: PKI QE
URL:
Whiteboard:
Depends On:
Blocks: 2001170
TreeView+ depends on / blocked
 
Reported: 2021-07-21 12:46 UTC by Chandan Pinjani
Modified: 2025-06-09 15:34 UTC (History)
5 users (show)

Fixed In Version: redhat-pki-10-8050020211123024958.240794ab
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2001170 (view as bug list)
Environment:
Last Closed: 2022-02-02 10:16:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker DOGTAG-585 0 None None None 2025-06-09 15:33:39 UTC
Red Hat Issue Tracker RHCS-2433 0 None None None 2021-09-03 18:19:06 UTC
Red Hat Product Errata RHEA-2022:0398 0 None None None 2022-02-02 10:16:46 UTC

Comment 7 Endi Sukma Dewata 2021-07-29 02:01:29 UTC
I see you have pki_import_admin_cert = False. Could you try removing it?

BTW, TFT-677 has been resolved so you should be able to test it on RHEL 9.

Comment 31 errata-xmlrpc 2022-02-02 10:16:24 UTC
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 (Red Hat Certificate System 10.3 General Availability), 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/RHEA-2022:0398

Comment 32 RHEL Program Management 2025-06-09 15:34:03 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.


Note You need to log in before you can comment on or make changes to this bug.