pki cert-request-find fails to provide proper results when Negative or very huge number is passed to start and size options
pki -d /opt/rhqa_pki/certs_db -n "CA_agentV" -c redhat123 cert-request-find --start -1
I see below output
------------------- 100 entries matched ------------------- Request ID: 10 Type: enrollment Request Status: complete Operation Result: success Certificate ID: 0xa Request ID: 11 Type: enrollment Request Status: complete Operation Result: success Certificate ID: 0xb Request ID: 12 Type: enrollment Request Status: complete Operation Result: success Certificate ID: 0xc Request ID: 13 Type: enrollment Request Status: complete Operation Result: success Certificate ID: 0xd Request ID: 14 Type: enrollment Request Status: complete Operation Result: success Certificate ID: 0xe Request ID: 15 Type: revocation Request Status: complete Operation Result: success .... .... .... ... ... Request ID: 27 Type: enrollment Request Status: pending Operation Result: success Request ID: 28 Type: enrollment Request Status: canceled Operation Result: success Request ID: 29 Type: enrollment Request Status: rejected Operation Result: success ----------------------------- Number of entries returned 20 -----------------------------
Shouldn't the results return 19 entries when -1 (pki cert-find reports 19 entries with --start -1)
[root@dhcp207-176 ~]# pki -d /opt/rhqa_pki/certs_db -n "CA_agentV" -c redhat123 cert-request-find --size -1 ------------------- 100 entries matched ------------------- ---------------------------- Number of entries returned 0 ----------------------------
pki -d /opt/rhqa_pki/certs_db -n CA_agentV -c redhat123 cert-request-find \ --start 0288162993285622387271551070785285307053227225947734295050376445272265661264559890041246511705504626238806421776607911409615567384405888512530407835588249236546430982290671304304656525627837105291554 ------------------- 100 entries matched ------------------- Request ID: 100 Type: enrollment Request Status: complete Operation Result: success Certificate ID: 0x3c ---------------------------- Number of entries returned 1 ----------------------------
propose Milestone 10.3
Per email discussions, propose Milestone 10.3.
Per Bug Triage of 05/05/2016: 10.4
Metadata Update from @mrniranjan: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue priority set to: minor (was: trivial) - Issue set to the milestone: FUTURE (was: UNTRIAGED)
Per 10.5.x/10.6 Triage: FUTURE
mharmsen: negative case
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/1634
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
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)
Login to comment on this ticket.