Bug 1511120

Summary: Misleading Error : Unexpected comma or semicolon found at the end of the DN string.
Product: Red Hat Enterprise Virtualization Manager Reporter: Anitha Udgiri <audgiri>
Component: ovirt-engine-extension-aaa-ldapAssignee: Ondra Machacek <omachace>
Status: CLOSED ERRATA QA Contact: Gonza <grafuls>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.0CC: lsurette, mgoldboi, mperina, pmatyas, pstehlik, Rhev-m-bugs, troels, ykaul
Target Milestone: ovirt-4.2.0Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-extension-aaa-ldap-1.3.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1513759 (view as bug list) Environment:
Last Closed: 2018-05-15 17:35:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1465463    
Bug Blocks: 1513759    

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:
ovirt-engine-extension-aaa-ldap-setup-1.3.6-1.el7ev.noarch
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.

https://access.redhat.com/errata/RHEA-2018:1485
Comment 7 Franta Kust 2019-05-16 13:08:11 UTC 
BZ<2>Jira Resync
Comment 8 Daniel Gur 2019-08-28 13:14:29 UTC 
sync2jira
Comment 9 Daniel Gur 2019-08-28 13:19:31 UTC 
sync2jira