Bug 998479 - Updated user information in OpenLDAP are not propagated to engine
Summary: Updated user information in OpenLDAP are not propagated to engine
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.3.0
Assignee: Ravi Nori
QA Contact: Ondra Machacek
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-19 12:11 UTC by Ondra Machacek
Modified: 2016-02-10 19:20 UTC (History)
11 users (show)

Fixed In Version: is15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-29 07:35:01 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 18886 0 None None None Never

Description Ondra Machacek 2013-08-19 12:11:07 UTC 
Description of problem:
When user's informations are updated in OpenLDAP then these informations
are not propagated to engine in internal(3600s). After ~12hours it is still not
propagated.

Version-Release number of selected component (if applicable):
is10

How reproducible:
always

Steps to Reproduce:
1. Have OpenLDAP with some user.
2. update users' information. (ie, email, or add/remove group to user)
3. Wait 3600s and check if informations are propageted to engine.

Actual results:
Informations are not propageted to rhevm.

Expected results:
Informations are propageted.

Additional info:
Comment 1 Ravi Nori 2013-09-09 19:54:25 UTC 
I have posted a fix for OpenLdap as I was only able to reproduce this for OpenLdap, worked fine for Ad, 389DS and FreeIPA.

Please let me know if the issue was seen only for OpenLdap or other ldap servers too.
Comment 2 Shai Revivo 2013-09-29 07:35:01 UTC 
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step
Note You need to log in before you can comment on or make changes to this bug.