Bug 1620164

Summary:	Better error when context not specified with `hammer user list` when specifying `--auth-source-ldap*`
Product:	Red Hat Satellite	Reporter:	Chris Hudson <chhudson>
Component:	Users & Roles	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Radovan Drazny <rdrazny>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.2	CC:	apatel, dhlavacd, kgaikwad, mbacovsk, mhulan, mshira, oprazak, rabajaj
Target Milestone:	Unspecified	Keywords:	Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-02 16:07:43 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 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.