Description of problem: When ldap connection fails, only generic error, which does not say much about root cause is shown. Version-Release number of selected component (if applicable): 6.4.2 How reproducible: 100% Steps to Reproduce: 1. Install Satellite 6.4 (or 6.5) with external ldap 2. break either dns resolution, network speed, overload ldap server... 3. try to login using ldap user Actual results: "Error while connecting to '%{name}' LDAP server at '%{url}' during authentication" % {:url => self.host, :name => self.name} [timestamp] [source host] [url called] [Error 500] Foreman::LdapException: ERF77-3544 [Foreman::LdapException]: Error while connecting to 'Ldapserver-Auth' LDAP server at 'ldap.server.test' during authentication ([Net::LDAP::Error]: Connection timed out - user specified timeout) Expected results: Get info on which step connection timeouted. was it name resolution, high network latency, ldap server response? It will help with troubleshooting a lot.
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
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 feel free to contact your Red Hat Account Team. Thank you.