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.
DescriptionAsha Akkiangady
2017-11-17 19:36:57 UTC
Description of problem:
pkispawn CA fails when the system is in FIPS mode.
Version-Release number of selected component (if applicable):
pki-ca-10.5.1-1.el7.noarch
pki-server-10.5.1-1.el7.noarch
How reproducible:
Steps to Reproduce:
1. RHEL 7.5 Server x86_64 system is enabled with FIPS.
2. pkispawn CA using 2 step install process (with hsm).
a. First step of pkispawn with pki_skip_configuration=True succeeds.
b. Apply the fips ssl ciphers as described in http://pki.fedoraproject.org/wiki/SSL and pkispawn with pki_skip_installation=True.
3. pkispawn hangs.
Actual results:
'pki_user': 'pkiuser',
'pki_user_deployment_cfg': 'ca_inst.inf',
'pki_user_deployment_cfg_replica': '/etc/sysconfig/pki/tomcat/rhcs92-CA-aakkiang-non-tms/ca/deployment.cfg',
'pki_user_deployment_cfg_spawn_archive': '/var/log/pki/rhcs92-CA-aakkiang-non-tms/ca/archive/spawn_deployment.cfg.20171117140524',
'resteasy_lib': u'/usr/share/java/resteasy-base',
'sensitive_parameters': '\npki_admin_password\npki_backup_password\npki_client_database_password\npki_client_pin\npki_client_pkcs12_password\npki_clone_pkcs12_password\npki_ds_password\npki_external_pkcs12_password\npki_pkcs12_password\npki_one_time_pin\npki_pin\npki_replication_password\npki_security_domain_password\npki_server_pkcs12_password\npki_token_password',
'spawn_scriplets': '\ninitialization\ninfrastructure_layout\ninstance_layout\nsubsystem_layout\nwebapp_deployment\nslot_substitution\nsecurity_databases\nselinux_setup\nconfiguration\nfinalization'}
pkispawn hung at this point.
No useful info in the pkispawn logs for the failure.
Expected results:
pkispawn should be successful.
Additional info:
The issue got resolved with the build openssl-1.0.2k-11.el7, attached to bug https://bugzilla.redhat.com/show_bug.cgi?id=1493178
Since there is no specific action necessary from RHCS side, closing this bug.