Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1620164 - Better error when context not specified with `hammer user list` when specifying `--auth-source-ldap*`
Summary: Better error when context not specified with `hammer user list` when specifyi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-22 15:03 UTC by Chris Hudson
Modified: 2019-10-02 16:07 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-02 16:07:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26414 0 None None None 2019-03-20 09:32:25 UTC

Description Chris Hudson 2018-08-22 15:03:44 UTC 
Description of problem:
When an organization is not specified when querying a sepcific ldap source, the generic error "undefined method `name' for nil:NilClass" is returned. It would be helpful to return something that lets the end user know that specifying an organization is required.


Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli_katello-0.11.3.5-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run `hammer user list --auth-source-ldap-id <ldap_id>`
2. View error
3.

Actual results:
# hammer user list --auth-source-ldap-id 3
undefined method `name' for nil:NilClass


Expected results:
Something like..

# hammer user list --auth-source-ldap-id 3
Error: Please specify organization


Additional info:
Comment 2 Ondřej Pražák 2019-03-20 09:32:25 UTC 
Created redmine issue http://projects.theforeman.org/issues/26414 from this bug
Comment 3 Bryan Kearney 2019-09-03 19:06:42 UTC 
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Comment 4 Bryan Kearney 2019-10-02 16:07:43 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Note You need to log in before you can comment on or make changes to this bug.