Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1600149 - CA Agent UI -> List Requests -> Starting request number: search field does not work as expected
Summary: CA Agent UI -> List Requests -> Starting request number: search field does no...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: RHCS Maintainers
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-11 14:16 UTC by Roshni
Modified: 2018-09-10 22:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
CA debug log during this issue (deleted)
2018-07-11 14:16 UTC, Roshni
no flags Details

Description Roshni 2018-07-11 14:16:17 UTC
Created attachment 1458123 [details]
CA debug log during this issue

Description of problem:
CA Agent UI -> List Requests -> Starting request number: search field does not work as expected

Version-Release number of selected component (if applicable):
pki-ca-10.5.9-1.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Access CA agent Web UI
2. Click List Requests
3. If you have a certificate request with request ID less than (decimal) 50, then enter 50 in the Starting request number box. 

Actual results:
Certificate request with request ID 27 is listed

Expected results:


Additional info:
I have a pending request with request ID 27. I tried various values in this field, attaching log messages when these values were tried.


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