+++ This bug was initially created as a clone of Bug #967890 +++ Description of problem: Sometimes even debug level doesn't provide enough information on possible issues. Version-Release number of selected component (if applicable): all How reproducible: Special corner case - AD test works fine, however JndiAction fails with No user information found error Steps to Reproduce: Have AD with another domain as Subtree. user in the subtree. Try to use the user and add the subtree domain via engine-manage-domains Actual results: Action fails and even in debug mode user cannot get enough information on the issue. Expected results: More info like User GUID, URI and ldapServerPath should be displayed in debug mode. --- Additional comment from Tomas Dosek on 2013-05-28 13:51:22 EDT --- Proposed patch: http://gerrit.ovirt.org/15139
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0038.html