Bug 998479

Summary: Updated user information in OpenLDAP are not propagated to engine
Product: Red Hat Enterprise Virtualization Manager Reporter: Ondra Machacek <omachace>
Component: ovirt-engineAssignee: Ravi Nori <rnori>
Status: CLOSED UPSTREAM QA Contact: Ondra Machacek <omachace>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, bazulay, iheim, lpeer, omachace, pstehlik, Rhev-m-bugs, rnori, srevivo, yeylon, yzaslavs
Target Milestone: ---Keywords: Triaged
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: is15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-29 07:35:01 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:

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