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:
A proper error message is not displayed when a non-existent request identifier is provided for "getcert list".
Version-Release number of selected component (if applicable):
[root@dhcp201-220 ~]# rpm -q certmonger
certmonger-0.48-1.el6.x86_64
[root@dhcp201-220 ~]#
How reproducible:
Always
Steps to Reproduce:
1.Install Certmonger and start certmonger service
2.run following command
[root@dhcp201-220 ~]# getcert list -i non-existent
Number of certificates and requests being tracked: 0.
[root@dhcp201-220 ~]#
Actual results:
It displays on command line only no of certificates tracked.
Expected results:
It should prompt that no matching request found for given request identifier.
Additional info:
(1)Similar behaviour observed when non-existent nickname along with existing NSS db is provided with 'getcert list'. In this case too it should prompt that no matching request found for given nickname.
[root@dhcp201-220 ~]# getcert list -d /tmp/kaleem/ -n non-existent
Number of certificates and requests being tracked: 0.
[root@dhcp201-220 ~]#
(2)Similar behaviour observed when non-existent file based storage is provided with 'getcert list'. In this scenario as well it should prompt that no matching request found for given file based storage.
[root@dhcp201-220 ~]# getcert list -f /tmp/kaleem/non-existent.crt
Number of certificates and requests being tracked: 0.
[root@dhcp201-220 ~]#
Nalin,
Still i see earlier behaviour and there is no new error message for this.
[root@dhcp201-220 ~]# rpm -q certmonger
certmonger-0.49-1.el6.x86_64
[root@dhcp201-220 ~]# getcert list -i non-existent
Number of certificates and requests being tracked: 0.
[root@dhcp201-220 ~]
Verified.
RHEL Version:
[root@dhcp201-220 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.2 Beta (Santiago)
Certmonger Version:
[root@dhcp201-220 ~]# rpm -q certmonger
certmonger-0.50-1.el6.x86_64
[root@dhcp201-220 ~]#
Steps used to verified:
(1)Install Certmonger
[root@dhcp201-220 ~]# yum install certmonger -y
Loaded plugins: product-id, subscription-manager
Installed:
certmonger.x86_64 0:0.50-1.el6 [root@dhcp201-220 ~]#
(2)Start Certmonger service
[root@dhcp201-220 ~]# service certmonger start
Starting certmonger: [ OK ]
[root@dhcp201-220 ~]#
(3)Run "getcert list" with a non-existent request identifier/nickname with NSS db/filebased storage
[root@dhcp201-220 ~]# getcert list -i non-existent
No request found with specified nickname.
[root@dhcp201-220 ~]#
[root@dhcp201-220 ~]# getcert list -d /tmp/kaleem/ -n non-existent
No request found that matched arguments.
[root@dhcp201-220 ~]#
[root@dhcp201-220 ~]# getcert list -f /tmp/kaleem/non-existent.crt
No request found that matched arguments.
[root@dhcp201-220 ~]#
Result:
Now proper error message is displayed on providing non-existent request identifier/nickname with NSS db or non-existent filebased storage.
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.
http://rhn.redhat.com/errata/RHBA-2011-1708.html