Hide Forgot
Description of problem: A proper error message should be displayed when a non-existent CA name 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 (non-existent CA name) [root@dhcp201-220 ~]# getcert list -c non-existent Number of certificates and requests being tracked: 2. [root@dhcp201-220 ~]# Actual results: It displays on command line only no of certificates tracked. Expected results: It should prompt that no such CA exists.
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 -c non-existent Number of certificates and requests being tracked: 0. [root@dhcp201-220 ~]#
Ugh, didn't push these changes from the box where they were made. Fixing.
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 CA name [root@dhcp201-220 ~]# getcert list -c non-existent No CA with name "non-existent" found. [root@dhcp201-220 ~]# Result: Now proper error message "No CA with name "non-existent" found." is displayed.
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