It looks like the upgrade caused files like these to be set back to default:
/usr/share/pki/ca/profiles/ca/caAgentServerCert.cfg /usr/share/pki/ca/profiles/ca/caECDirUserCert.cfg /usr/share/pki/ca/conf/caAuditSigningCert.profile /usr/share/pki/ca/profiles/ca/caInternalAuthSubsystemCert.cfg /usr/share/pki/ca/profiles/ca/caECDirUserCert.cfg /usr/share/pki/ca/profiles/ca/caInternalAuthSubsystemCert.cfg and a bunch of other files in there and /var/lib/pki/pki-tomcat/
It looks like the upgrade overwrote a bunch of config files, changes were rather small.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1494530 - Custom field type adjusted to None - Custom field version adjusted to None - Issue priority set to: critical - Issue set to the milestone: 10.5
[20171025] - edewata commented * looks like there’s a broken/missing upgrade scripts, and missing database upgrade instruction
Metadata Update from @mharmsen: - Issue assigned to mharmsen
Metadata Update from @mharmsen: - Issue assigned to edewata (was: mharmsen)
NOTE: Until and unless this conditions in the associated bug can be reproduced, this ticket is scheduled to be closed invalid in one to two weeks.
Per PKI Team Meeting of 20180118 closed invalid
Metadata Update from @mharmsen: - Issue close_status updated to: invalid - Issue set to the milestone: 10.5.4 (was: 10.5) - 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/2961
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.