Bug 1511120 – Misleading Error : Unexpected comma or semicolon found at the end of the DN string.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine-extension-aaa-ldap (Show other bugs)
Sub Component:
Version:	4.1.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	ovirt-4.2.0
Target Release:	---
Assigned To:	Ondra Machacek
QA Contact:	Gonza
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	1465463
Blocks:	1513759
	Show dependency tree / graph

Reported:	2017-11-08 12:54 EST by Anitha Udgiri
Modified:	2018-05-15 13:36 EDT (History)
CC List:	8 users (show)

See Also:
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:
Clones:	1513759 (view as bug list)
Environment:
Last Closed:	2018-05-15 13:35:42 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2018:1485	None	None	None	2018-05-15 13:36 EDT

Groups: None (edit)

Description Anitha Udgiri 2017-11-08 12:54:37 EST

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 10:12:40 EST

Verified with:
ovirt-engine-extension-aaa-ldap-setup-1.3.6-1.el7ev.noarch

Comment 6 errata-xmlrpc 2018-05-15 13:35:42 EDT

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

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