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 1486870 - Lightweight CA key replication fails (regressions) [RHEL 7.4.z]
Summary: Lightweight CA key replication fails (regressions) [RHEL 7.4.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Fraser Tweedale
QA Contact: Asha Akkiangady
Petr Bokoc
URL:
Whiteboard:
Depends On: 1484359
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-30 16:24 UTC by Tom Lavigne
Modified: 2017-11-30 15:32 UTC (History)
7 users (show)

Fixed In Version: pki-core-10.4.1-14.el7_4
Doc Type: Bug Fix
Doc Text:
A previous update to one of the key unwrapping functions introduced a requirement for a key usage parameter which was not being supplied at the call site, which caused lightweight CA key replication to fail. This bug has been fixed by modifying the call site so that it supplies the key usage parameter, and lightweight CA key replication now works as expected.
Clone Of: 1484359
Environment:
Last Closed: 2017-11-30 15:32:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
console.log (24.15 KB, text/plain)
2017-09-25 06:48 UTC, Abhijeet Kasurde
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3301 0 normal SHIPPED_LIVE pki-core bug fix and enhancement update 2017-11-30 20:14:57 UTC

Description Tom Lavigne 2017-08-30 16:24:56 UTC
This bug has been copied from bug #1484359 and has been proposed
to be backported to 7.4 z-stream (EUS).

Comment 6 Fraser Tweedale 2017-09-22 06:50:31 UTC
Add doc text.

Comment 7 Abhijeet Kasurde 2017-09-25 06:47:41 UTC
Verified using IPA and PKI version::

# rpm -qa ipa-server selinux-policy pki-*
ipa-server-4.5.0-21.el7_4.2.2.x86_64
pki-kra-10.4.1-15.el7_4.noarch
selinux-policy-3.13.1-166.el7_4.5.noarch
pki-base-java-10.4.1-15.el7_4.noarch
pki-tools-10.4.1-15.el7_4.x86_64
pki-server-10.4.1-15.el7_4.noarch
pki-base-10.4.1-15.el7_4.noarch
pki-ca-10.4.1-15.el7_4.noarch

Marking BZ as verified. Please see attachment for console log.

Comment 8 Abhijeet Kasurde 2017-09-25 06:48:12 UTC
Created attachment 1330369 [details]
console.log

Comment 11 errata-xmlrpc 2017-11-30 15:32:00 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, 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:3301


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