What is being shown below appears to represent a regression between Dogtag 10.2.5 /10.2.6 packages and Dogtag 10.3.x packages:
[root@pki1 ~]# pki-server subsystem-cert-find ca Traceback (most recent call last): File "/usr/sbin/pki-server", line 107, in <module> cli.execute(sys.argv) File "/usr/sbin/pki-server", line 102, in execute super(PKIServerCLI, self).execute(args) File "/usr/lib/python2.7/site-packages/pki/cli/init.py", line 203, in execute module.execute(module_args) File "/usr/lib/python2.7/site-packages/pki/cli/init.py", line 203, in execute module.execute(module_args) File "/usr/lib/python2.7/site-packages/pki/cli/init.py", line 203, in execute module.execute(module_args) File "/usr/lib/python2.7/site-packages/pki/server/cli/subsystem.py", line 377, in execute results = subsystem.find_system_certs() AttributeError: 'NoneType' object has no attribute 'find_system_certs'
Per PKI Bug Council of 06/23/2016: 10.3.4
The error is caused by a non-default instance name used in the test. By default the CLI will use pki-tomcat instance name. When the correct instance name is specified with -i option the command works fine. The CLI should be fixed to display a more helpful error message, e.g. "Instance not found: pki-tomcat".
The pki-server subsystem-cert-update is actually failing due to a bug in the code.
Pushed to master (67bbdc5edd1404f89e638037599b4231f50490f8)
Metadata Update from @rpattath: - Issue assigned to edewata - Issue set to the milestone: 10.3.4
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/2505
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.