Bug 782743 - search users returns all objects from AD (only during 1st use)
Summary: search users returns all objects from AD (only during 1st use)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: 3.1
Assignee: Daniel Erez
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-18 10:57 UTC by Pavel Stehlik
Modified: 2012-08-09 08:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 08:01:47 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description Pavel Stehlik 2012-01-18 10:57:05 UTC
Description of problem:
 When trying to add user - searching in AD & put there 'porta' => GO then it returns whole object list (groups & users). When clicking on GO buttone for 2nd time, it returns correct data.
When using 'internal' domain, then always is returned ADMIN.
UserPortal behaves correctly.


Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-3.0.0_0001-1.2.fc16.x86_64

How reproducible:
follow above steps

Steps to Reproduce:
1.
2.
3.
  
Actual results:
returns all objects 

Expected results:
should return correct users/groups


Additional info:

Comment 1 Einav Cohen 2012-01-18 12:31:18 UTC
It seems that after the first "GO", the value that is used for the users-search is the "old" text-box value (i.e. empty string), so everything is being returned.

In the second time, the value that is used for the users-search is the correct one from the text box.

Comment 2 Daniel Erez 2012-01-24 10:48:24 UTC
commit c20d4adbe79fa1aaee6616a2ba0c66535eace29c

Comment 3 Itamar Heim 2012-08-09 08:01:47 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/

Comment 4 Itamar Heim 2012-08-09 08:03:21 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/


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