Bug 665143 - Bad return values for ipa-rmkeytab command.
Summary: Bad return values for ipa-rmkeytab command.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: ipa
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Rob Crittenden
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 667210
TreeView+ depends on / blocked
 
Reported: 2010-12-22 20:50 UTC by Gowrishankar Rajaiyan
Modified: 2012-03-27 06:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 667210 (view as bug list)
Environment:
Last Closed: 2012-03-27 06:51:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gowrishankar Rajaiyan 2010-12-22 20:50:50 UTC
Description of problem:
Bad return values for ipa-rmkeytab command while using the "-r" option.

Version-Release number of selected component (if applicable):
ipa-admintools-1.91-0.2010121421gitcec6703.fc14.x86_64

How reproducible:


Steps to Reproduce:
1. ipa-rmkeytab -r INVALID-REALM-NAME -k /opt/krb5.keytab
Actual results:
echo $? = 0 and no info in terminal. 
Expected results:
Non-zero exit status with a message "realm name not found in keytab" as info in terminal.

2. ipa-rmkeytab -r $VALID-REALM -k $KEYTAB-IS-A-TXT-FILE 
Actual result:
echo $?=0 and no info in terminal.
Expected results:
Exit status as 3, with the message "Failed to open keytab". 

Additional info:

Comment 1 Dmitri Pal 2010-12-22 23:53:16 UTC
https://fedorahosted.org/freeipa/ticket/654

Comment 2 Rob Crittenden 2011-01-07 14:40:50 UTC
problem #1 moved to bug https://bugzilla.redhat.com/show_bug.cgi?id=667210

problem #2 addressed in a1188d95e8e318ebb70181fdb0d03e0485949b26

Comment 3 Jenny Severance 2011-03-01 19:09:17 UTC
Verified

version:
ipa-server-2.0.0-13.el6.x86_64

[root@ipaqavmh ~]# ipa-rmkeytab -r TESTRELM -k /opt/krb5.keytab
Failed to open keytab '/opt/krb5.keytab': No such file or directory

[root@ipaqavmh ~]# echo $?
3


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