Bug 1064395

Summary: search paging on event log does not use paging correctly
Product: [Retired] oVirt Reporter: Eli Mesika <emesika>
Component: ovirt-engine-coreAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Belka <jbelka>
Severity: high Docs Contact:
Priority: high    
Version: 3.4CC: acathrow, gklein, iheim, jbelka, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: ovirt-3.4.0-rc Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 12:28:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eli Mesika 2014-02-12 14:18:15 UTC
Description of problem:

search paging on event log does not use paging correctly 
If we browse to 2nd page from UI Events TAB by pressing the '>' button and then put "Vms: page 1" as the search text , we get the following error


2014-02-12 16:11:23,365 WARN  [org.ovirt.engine.core.bll.SearchQuery] (ajp--127.0.0.1-8702-14) ResourceManager::searchBusinessObjects - erroneous search text - Events:page 1 page 2


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


How reproducible:


Steps to Reproduce:
1. Have more than 100 events or tweak page size to a smaller value in DB
2. start engine
3. select Events 
4. click on the paging next page button ('>')
5. write as the search text "Vms: page 1" and click enter

Actual results:
2014-02-12 16:11:23,365 WARN  [org.ovirt.engine.core.bll.SearchQuery] (ajp--127.0.0.1-8702-14) ResourceManager::searchBusinessObjects - erroneous search text - Events:page 1 page 2

Expected results:
Page 1 should be displayed 

Additional info:

Comment 1 Itamar Heim 2014-02-16 08:23:09 UTC
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Sandro Bonazzola 2014-03-03 14:40:08 UTC
This BZ should be fixed in oVirt 3.4.0 RC

Comment 3 Jiri Belka 2014-03-18 14:18:42 UTC
ok, av3 & rhel6.

Comment 4 Sandro Bonazzola 2014-03-31 12:28:45 UTC
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released