Steps to reproduce.
for i in $(seq 1 17); do pki -d /opt/rhqa_pki/certs_db -c Secret123 -h \ dhcp207-176.lab.eng.pnq.redhat.com -p 30044 -n "KRA3_agentR" key-generate \ temp0-$i --key-algorithm AES --key-size 128 --usages wrap; done
pki -d /opt/rhqa_pki/certs_db -c Secret123 -p 30044 -h \ dhcp207-176.lab.eng.pnq.redhat.com -n "KRA3_agentV" key-request-find --maxResults 5 ------------------ 16 entries matched ------------------ Request ID: 0x1 Key ID: 0x1 Type: symkeyGenRequest Status: complete Request ID: 0x2 Key ID: 0x2 Type: symkeyGenRequest Status: complete Request ID: 0x3 Key ID: 0x3 Type: symkeyGenRequest Status: complete ... ... .. .... ----------------------------- Number of entries returned 16 -----------------------------
Per CS/DS meeting of 08/25/2014: 10.2.3
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3
NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.
Per Bug Triage of 05/05/2016: 10.3.1
Cannot reproduce; correct number of results in returned with --maxResults <N>. Closing WFM.
--maxResults <N>
Metadata Update from @mrniranjan: - Issue assigned to ftweedal - Issue set to the milestone: 10.3.2
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/1687
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.
Login to comment on this ticket.