After upgrading CA, web interface displays 500 error with "java.io.IOException: CS server is not ready to serve." trace.
Steps to Reproduce:
1. Install Certificate System using previous bits as available through repository. 2. Upgrade to pending release bits using yum install yum install ./pki-* 3. Attempt to access web interface
Actual results:
500 error
Expected results:
Links to EE or agent interface.
Additional info:
Restarting pki-tomcat does not work, only restarting firewalld or system reboot fixes the issue.
Metadata Update from @dsirrine: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue priority set to: 3 - Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)
Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.
Metadata Update from @mharmsen: - Issue set to the milestone: FUTURE (was: 10.4)
Per PKI Triage of 8/31/2017, closing as WORKSFORME (alee).
Metadata Update from @mharmsen: - Issue close_status updated to: worksforme - 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/2715
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.