Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1511120 - Misleading Error : Unexpected comma or semicolon found at the end of the DN string.
Summary: Misleading Error : Unexpected comma or semicolon found at the end of the DN s...
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-extension-aaa-ldap
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.2.0
: ---
Assignee: Ondra Machacek
QA Contact: Gonza
Depends On: 1465463
Blocks: 1513759
TreeView+ depends on / blocked
Reported: 2017-11-08 17:54 UTC by Anitha Udgiri
Modified: 2018-05-15 17:36 UTC (History)
8 users (show)

Fixed In Version: ovirt-engine-extension-aaa-ldap-1.3.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1513759 (view as bug list)
Last Closed: 2018-05-15 17:35:42 UTC
oVirt Team: Infra
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1485 None None None 2018-05-15 17:36:13 UTC

Description Anitha Udgiri 2017-11-08 17:54:37 UTC
Description of problem:
We have been having quite a few customers off late reporting setup issues with the error as defined in summary.

In all these cases, we have seen that the underlying error is something different but the customer sees only "Unexpected comma or semicolon found at the end of the DN string."

This error is very misleading and they are unable to determine the exact cause until we at support ask for debug logs to determine the actual cause.

In one of the case, the actual problem was : The connection reader was unable to successfully complete TLS negotiation:  LDAPException(resultCode=91 (connect error), errorMessage='Hostname verification failed because the expected hostname '<fqdn>' was not found in peer certificate..."

We need some changes to showcase the actual error at these times.

Comment 3 Gonza 2018-01-29 15:12:40 UTC
Verified with:

Comment 6 errata-xmlrpc 2018-05-15 17:35:42 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.