The SystemConfigService.configure() is quite large. If the method returns a generic error or hangs, troubleshooting will be difficult because we will need to follow the execution progress in the debug log. The start of the execution might be quite far from where the error occurs.
It might be better to split the method into smaller methods such as configureDatabase(), configureCA(), configureTPS(), etc. State objects can be passed around as session attributes, it's not necessary to save them into CS.cfg. This way the client (pkispawn) will have more control on the process and it will also narrow down the troubleshooting scope. It will also allow calling specific methods to partially reconfigure the instance if necessary.
Metadata Update from @edewata: - Issue set to the milestone: FUTURE
This is a continuous improvement, no need to keep track.
Metadata Update from @edewata: - Custom field feature adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/1333
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.