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.

Bug 1052860

Summary: No error message with invalid sid given to trust-resolve
Product: Red Hat Enterprise Linux 7 Reporter: Steeve Goveas <sgoveas>
Component: ipaAssignee: Martin Kosek <mkosek>
Status: CLOSED CURRENTRELEASE QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0CC: dpal, rcritten
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-3.3.3-13.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 11:45:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steeve Goveas 2014-01-14 09:11:27 UTC
Description of problem:
trust-resolve does not throw an error when an invalid sid is given

Version-Release number of selected component (if applicable):
ipa-server-3.3.3-10.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Setup Trust
2. Run command with SID as userSID
# ipa trust-resolve --sids userSID
# echo $?
0

# ipa trust-resolve
Security Identifiers (SIDs): NoSID
# echo $?
0

Actual results:
No error reported

Expected results:
Error expected

Comment 2 Martin Kosek 2014-01-14 11:37:36 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4113

Comment 3 Martin Kosek 2014-01-20 17:26:26 UTC
Fixed upstream:
master: https://fedorahosted.org/freeipa/changeset/511a5f248b173198ee77df9589a7922b2c890e24
ipa-3-3: https://fedorahosted.org/freeipa/changeset/014ccb13b6cfad6c03733104ecc3d288a2ce7a8c

Note that after a discussion, we rather decided to hide trust-resolve as internal command. See

​http://www.redhat.com/archives/freeipa-devel/2014-January/msg00211.html

Comment 5 Steeve Goveas 2014-01-22 09:26:53 UTC
[root@hp-bl280cg6-01 ~]# ipa trust-resolve
ipa: ERROR: unknown command 'trust-resolve'

[root@hp-bl280cg6-01 ~]# ipa help trust | grep resolv
[root@hp-bl280cg6-01 ~]# echo $?
1

[root@hp-bl280cg6-01 ~]# ipa trust-resolve --help
ipa: ERROR: unknown command 'trust-resolve'

[root@hp-bl280cg6-01 ~]# ipa help trust-resolve 
ipa: ERROR: no command nor help topic 'trust_resolve'

Verified in version

[root@hp-bl280cg6-01 ~]# rpm -q ipa-server
ipa-server-3.3.3-13.el7.x86_64

Comment 6 Ludek Smid 2014-06-13 11:45:42 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.