Bug 1064395 - search paging on event log does not use paging correctly
Summary: search paging on event log does not use paging correctly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.4.0
Assignee: Ravi Nori
QA Contact: Jiri Belka
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-12 14:18 UTC by Eli Mesika
Modified: 2014-03-31 12:28 UTC (History)
5 users (show)

Fixed In Version: ovirt-3.4.0-rc
Clone Of:
Environment:
Last Closed: 2014-03-31 12:28:45 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


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

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


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