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 1692253 - CA ECC installation is fail on LunaSA machine
Summary: CA ECC installation is fail on LunaSA machine
Keywords:
Status: CLOSED DUPLICATE of bug 1655438
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pki-core
Version: 8.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 8.0
Assignee: RHCS Maintainers
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-25 07:20 UTC by Deepak Punia
Modified: 2019-05-22 05:08 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-29 00:44:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
installation Log (97.81 KB, text/plain)
2019-03-25 07:20 UTC, Deepak Punia
no flags Details
debug.log (26.75 KB, text/plain)
2019-03-25 07:21 UTC, Deepak Punia
no flags Details

Description Deepak Punia 2019-03-25 07:20:30 UTC
Created attachment 1547605 [details]
installation Log

Description of problem:
[RHEL8.0] CA  ECC installation is failing on Safenet LunaSA HSM machine. also same scenario is working fine for CA RSA installation on Safenet LunaSA HSM.
Also tested with endi's copr bits as well it's not working.


Version-Release number of selected component (if applicable):
[root@ipaqavmg ca]# rpm -qi pki-ca
Name        : pki-ca
Version     : 10.6.10
Release     : 1.el8
Architecture: noarch
Install Date: Friday 22 March 2019 02:09:49 AM EDT
Group       : Unspecified
Size        : 2437207
License     : GPLv2 and LGPLv2
Signature   : (none)
Source RPM  : pki-10.6.10-1.el8.src.rpm
Build Date  : Friday 15 March 2019 07:39:13 PM EDT
Build Host  : copr-vm-production-os-00164974-20190315-232745
Relocations : (not relocatable)
Packager    : Red Hat Copr
Vendor      : dogtag
URL         : http://www.dogtagpki.org/
Summary     : PKI CA Package


How reproducible:
Install the CA ECC on LunaSA machine.


Steps to Reproduce:
1. Install the DS on LunaSA machine 
2. Do the CA installation on LunaSA machine with ECC


Actual results: 
CA Installation getting failed with ecc. 


Expected results:
Installation should be successful. 


Additional info: 
Attached is the installation & debug log.

Comment 1 Deepak Punia 2019-03-25 07:21:10 UTC
Created attachment 1547606 [details]
debug.log

Comment 3 Deepak Punia 2019-03-25 13:42:37 UTC
Above Bug is Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1655438

Comment 4 Asha Akkiangady 2019-03-29 00:44:41 UTC

*** This bug has been marked as a duplicate of bug 1655438 ***


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