Per IRC discussion, this will be addressed in IPA:
https://pagure.io/freeipa/issue/8503

This is actually the intended behavior of pkispawn:

• In normal (i.e. most) cases pkispawn will only generate the essential information (e.g. installation summary) to stdout.
• pkispawn performs some validations which will show an simple error message which should address the majority of trivial user errors.
• In case there's an error in unexpected places, pkispawn will generate a stack trace which points exactly where the issue happens in the code which is hopefully sufficient to troubleshoot trivial bugs.
• If necessary, pkispawn can be rerun in verbose mode to get some high-level context about what happened preceding to the error, which hopefully will address most user errors.
• If that's not sufficient, pkispawn can be rerun in debug mode to get more details which hopefully will generate enough information to troubleshoot the issue without direct access to the server.
• If that is still not sufficient, it would be necessary to get a direct access to the server,
  or to replicate the problem on a local machine.

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/3329

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.