Following kind of conversation is quite common on freeipa-users list:
user: 'IPA reports an internal error, what should I do?' dev: 'see HTTPd error log on the IPA server' user: 'what server?' dev: 'enable debugging on client and see to which server the client connected to'
We can eliminate this kind of ping-pong by using existing ServerInternalError exception instead of InternalError:
ServerInternalError
InternalError
ipalib/errors.py:class ServerInternalError(PublicError): ipalib/errors.py: >>> raise ServerInternalError(server='https://localhost') ipalib/errors.py: ServerInternalError: an internal error has occurred on server at 'https://localhost'
Apparently somebody was thinking about it in the past but ServerInternalError is currently not used anywhere.
Client should translate InternalError to ServerInternalError with appropriate server name and the error message should contain additional hint like this: See httpd error log on server %s for more details.
See httpd error log on server %s for more details.
Related discussion: https://www.redhat.com/archives/freeipa-devel/2015-April/msg00228.html
Processing leftovers from 4.2 backlog - this ticket was found as suitable for consideration in next big feature release - 4.4.
Metadata Update from @pspacek: - Issue assigned to someone - Issue set to the milestone: FreeIPA 4.5 backlog
Login to comment on this ticket.