Hide Forgot
Description of problem: When no value is provided to --revocation-reason argument in ipa cert_revoke, following unhelpful error message displayed. [root@ipa63server ipa-cert]# ipa cert-revoke 5 --revocation-reason= ipa: ERROR: an internal error has occurred [root@ipa63server ipa-cert] Version-Release number of selected component (if applicable): [root@ipa63server ipa-cert]# rpm -q ipa-server ipa-server-2.2.0-5.el6.x86_64 [root@ipa63server ipa-cert]# How reproducible: Always Steps to Reproduce: 1.Install IPA server 2.Try to revoke certificate with 'ipa cert-revoke' and provide no value to --revocation-reason optional argument. [root@ipa63server ipa-cert]# ipa cert-revoke 5 --revocation-reason= ipa: ERROR: an internal error has occurred [root@ipa63server ipa-cert Actual results: Got following error message "ipa: ERROR: an internal error has occurred" Expected results: Some helpful error message should be displayed
Upstream ticket: https://fedorahosted.org/freeipa/ticket/2597
Fixed upstream: master: https://fedorahosted.org/freeipa/changeset/51b34d5c4249e540510993fe600d222f22fcda16 ipa-2-2: https://fedorahosted.org/freeipa/changeset/66317ac7ca4a21fd1055f3ff971ab03dc5ea9a43
Verified. ipa-server version: [root@ipa63server ~]# rpm -q ipa-server ipa-server-2.2.0-9.el6.x86_64 [root@ipa63server ~]# Now proper error message is displayed when empty --revocation-reason is provided. [root@ipa63server ~]# ipa cert_revoke 5 --revocation-reason= ipa: ERROR: 'revocation_reason' is required [root@ipa63server ~]# Automated: :: [ PASS ] :: clear kerberos tkts service_12812/ipa63server.testrelm.com=12 12 ipa: ERROR: 'revocation_reason' is required :: [ PASS ] :: revocation_reason argument can not be empty 0xC 0xC ipa: ERROR: 'revocation_reason' is required :: [ PASS ] :: revocation_reason argument can not be empty
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No documentation needed.
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-2012-0819.html