#2754 cert-request-find --size 1 --status pending returns all results instead of 1 entry.
Closed: migrated by dmoluguw. Opened by mharmsen.

While finding the certificate request entries which is in pending status shows
all entries when --size 1 is provided.

Steps to Reproduce:

1. Enroll some certificate entries.
2. pki -d /root/multihost_tests/certdb/ -h pki1.example.com -p 20080 -c
    Secret123 -n "PKI CA Administrator for Example.Org" cert-request-find --size 1
    --status pending

Actual results:

-----------------
4 entries matched
-----------------
  Request ID: 68
  Type: enrollment
  Request Status: pending
  Operation Result: success
  Request ID: 69
  Type: enrollment
  Request Status: pending
  Operation Result: success
  Request ID: 78
  Type: enrollment
  Request Status: pending
  Operation Result: success
  Request ID: 79
  Type: enrollment
  Request Status: pending
  Operation Result: success
----------------------------
Number of entries returned 4
----------------------------
[root@pki1 ~]#

Expected results:

-----------------
4 entries matched
-----------------
  Request ID: 68
  Type: enrollment
  Request Status: pending
  Operation Result: success
----------------------------
Number of entries returned 1
----------------------------
[root@pki1 ~]#

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1464014
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: critical
- Issue set to the milestone: 10.4

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2874

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata