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.
Bug 807659 - Error message should be changed for ipa cert-revoke
Summary: Error message should be changed for ipa cert-revoke
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-28 12:27 UTC by Kaleem
Modified: 2012-03-28 13:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-28 13:38:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kaleem 2012-03-28 12:27:42 UTC
Description of problem:

[root@ipa63server ~]# ipa cert-revoke 5 3 --revocation-reason=6
ipa: ERROR: command 'cert_revoke' takes at most 1 argument

Here error message looks not correct as cert_revoke takes 2 arguments which are as follows.
 1. SERIAL-NUMER
 2. --revocation-reason

if --revocation-reason not provided , default value "0" is picked.

[root@ipa63server ~]# ipa help cert-revoke
Purpose: Revoke a certificate.
Usage: ipa [global-options] cert-revoke SERIAL-NUMBER [options]

Positional arguments:
  SERIAL-NUMBER         Serial number in decimal or if prefixed with 0x in
                        hexadecimal

Options:
  -h, --help            show this help message and exit
  --revocation-reason=INT
                        Reason for revoking the certificate (0-10)
[root@ipa63server ~]#

Version-Release number of selected component (if applicable):
[root@ipa63server ~]# rpm -q ipa-server
ipa-server-2.2.0-5.el6.x86_64
[root@ipa63server ~]#

How reproducible:
Always

Steps to Reproduce:
1.Run following command after ipa-server-install and observe

[root@ipa63server ~]# ipa cert-revoke 5 3 --revocation-reason=6
  
Actual results:
[root@ipa63server ~]# ipa cert-revoke 5 3 --revocation-reason=6
ipa: ERROR: command 'cert_revoke' takes at most 1 argument

Expected results:
Error message should be like 
"ipa: ERROR: command 'cert_revoke' takes at most 2 argument"

Comment 2 Rob Crittenden 2012-03-28 13:14:31 UTC
The two arguments are 5 and 3. You can only revoke one certificate at a time.

Comment 4 Rob Crittenden 2012-03-28 13:31:02 UTC
It isn't complaining about the revocation reason, two separate arguments were passed and it is correctly complaining about it.

This distinguishes options (dashed) and positional arguments.

Comment 5 Jenny Severance 2012-03-28 13:38:40 UTC
Got it, okay - let's close not a bug


Note You need to log in before you can comment on or make changes to this bug.