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.
Description of problem:
After NSS update requesting certificates using ipa-getcert with NSSDB storage type is not working. Request status: NEED_KEY_PAIR
Version-Release number of selected component (if applicable):
nss-3.16.1-4.el6_5.x86_64 update to 3.16.1-7.el6_5.x86_64
nss-softokn-3.14.3-9.el6.x86_64 update to 3.14.3-12.el6_5.x86_64
nss-softokn-freebl-3.14.3-9.el6.x86_6 update to 3.14.3-12.el6_5.x86_64
nss-sysinit-3.16.1-4.el6_5.x86_64 update to 3.16.1-7.el6_5.x86_64
nss-tools-3.16.1-4.el6_5.x86_64 update to 3.16.1-7.el6_5.x86_64
nss-util-3.16.1-1.el6_5.x86_64 update to 3.16.1-2.el6_5.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
After NSS update requesting certificates using ipa-getcert is not working. Request status: NEED_KEY_PAIR
Expected results:
Certificate request should succeed.
Additional info:
After restarting certmonger service certificate requests were processed.
OS used was Scientific Linux 6.5.
Comment 2Elio Maldonado Batiz
2015-10-08 23:04:41 UTC
(In reply to Raul Laansoo from comment #0)
> Description of problem:
>
> After NSS update requesting certificates using ipa-getcert with NSSDB
> storage type is not working. Request status: NEED_KEY_PAIR
>
> Version-Release number of selected component (if applicable):
>
> nss-3.16.1-4.el6_5.x86_64 update to 3.16.1-7.el6_5.x86_64
> nss-softokn-3.14.3-9.el6.x86_64 update to 3.14.3-12.el6_5.x86_64
> nss-softokn-freebl-3.14.3-9.el6.x86_6 update to 3.14.3-12.el6_5.x86_64
> nss-sysinit-3.16.1-4.el6_5.x86_64 update to 3.16.1-7.el6_5.x86_64
> nss-tools-3.16.1-4.el6_5.x86_64 update to 3.16.1-7.el6_5.x86_64
> nss-util-3.16.1-1.el6_5.x86_64 update to 3.16.1-2.el6_5.x86_64
>
>
> Actual results:
> After NSS update requesting certificates using ipa-getcert is not working.
> Request status: NEED_KEY_PAIR
Hi Raul, The current versions of the packages as of rhel-6.7 are
nss-3.19.1-3.el6_6.x86_64
nss-softokn-3.14.3-22.el6_6.x86_64
nss-util-3.19.1-1.el6_6.x86_64
nspr-4.10.8-1.el6_6.x86_64
certmonger-0.77.5-1.el6.x86_64
Have you tried those
>
> Expected results:
> Certificate request should succeed.
>
> Additional info:
> After restarting certmonger service certificate requests were processed.
> OS used was Scientific Linux 6.5.
Are you saying that a certmoger service restart makes the problem go away?
Comment 3Elio Maldonado Batiz
2015-10-09 00:11:46 UTC
With a fresh install of everything I tried:
1) With sqlite based shared db
# ipa-getcert request -d sql:/etc/pki/nssdb -n Server-Cert4Test
New signing request "20151009000504" added.
2) and with old legacy db
# ipa-getcert request -d /etc/pki/nssdb -n Server-Cert4TestLegacy
New signing request "20151009000537" added.
I don't see the status: NEED_KEY_PAIR.
Hi.
The problem I had was that after *updating* NSS packages to this particular version the requests did not work. The problem is related to the package upgraded process when after upgrade related services (ie certmonger) were not restarted.
HTH
Raul
Comment 7Kai Engert (:kaie) (inactive account)
2016-05-27 12:57:58 UTC
Hello Raul, I'm sorry this bug hasn't seen progress for a long time.
Thank you for your report, that restarting certain components might be required after updating NSS.
It might be difficult to track all services that potentially need to be restarted after a central component like NSS gets updated.
Perhaps NSS updates should go with the general recommendation to perform a reboot after an upgrade. I will forward that suggestion for discussion.
I'm reassining this to the certmonger component, so they can be aware of this scenario.
For testing try this:
- yum downgrade nss
- yum -y install certmonger
- service certmonger start (you don't need to have certs tracked)
- ps -ef |grep certmonger, note the pid
- yum update nss
- ps -ef |grep certmonger, the pid should be different indicating a service restart
Comment 14Abhijeet Kasurde
2016-11-30 09:28:40 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://rhn.redhat.com/errata/RHBA-2017-0663.html