Bug 988012 - Foreman Integration: search hosts on external provider foreman returns same results all the time
Summary: Foreman Integration: search hosts on external provider foreman returns same ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3
Assignee: Oved Ourfali
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-24 14:22 UTC by Eyal Edri
Modified: 2013-09-23 07:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 988001
Environment:
Last Closed: 2013-09-23 07:32:07 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
engine log file (620.03 KB, text/x-log)
2013-07-24 14:22 UTC, Eyal Edri
no flags Details


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

Description Eyal Edri 2013-07-24 14:22:12 UTC
Created attachment 777818 [details]
engine log file

Description of problem:

searching for hosts always returns the same output (list of hosts).
no matter what the search query is. 


Version:
ovirt-engine-3.3.0-0.3.beta1.fc19.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1. add external provider foreman to the system
2. click on add new host 
3. choose to use external providers
4. choose foreman
5. search for "host=hostname.." (where hostname is an existing host in your foreman). 
6. click on the search button
7. see results - it will return a list of hosts (probably the list of all hosts in the foreman, but still not all of them (could be it's limited in size)

Actual results:


Expected results:


Additional info:

Comment 1 Itamar Heim 2013-08-21 16:40:06 UTC
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)

Comment 2 Itamar Heim 2013-09-23 07:32:07 UTC
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)


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