Upgrading pki fails on Fedora 31:
# pki-server-upgrade WARNING: The pki-server-upgrade has been deprecated. Use pki-server upgrade instead. Upgrading from version 10.8.2 to 10.8.3: 1. Fix EC admin certificate profile (Yes/No) [Y]: Y ERROR: expected str, bytes or os.PathLike object, not NoneType Failed upgrading pki-tomcat/ca subsystem. Continue (Yes/No) [Y]? Y Upgrading version 10.8.3: No upgrade scriptlets. Tracker has been set to version 10.8.3. Upgrade complete. [root@id ~]# rpm -q pki-base pki-base-10.8.3-1.fc31.noarch
The same happens with pki-server upgrade, so it must be some common code.
pki-server upgrade
This is being addressed in this ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1814242
Metadata Update from @edewata: - 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 type adjusted to None - Custom field version adjusted to None
There are 2 possible solutions as we discussed.
(1) Ignore the missing property in CS.cfg.. This means, the admin purposefully removed it OR was removed automatically (as the OP observed). In either case, the admin is not worried about this profile
(2) Add the missing lines to CS.cfg. This means, the admin purposefully removed it (and chances are he/she deleted the corresponding caAdminCert.cfg). So, this might be problematic during the starting of the CA server.
caAdminCert.cfg
In my opinion, (1) seems the easy and safe approach. (2) seems to be risky, with unintended consequences for admin.
My 2c :smile:
Fixed via PR: https://github.com/dogtagpki/pki/pull/355
Metadata Update from @dmoluguw: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @dmoluguw: - Issue assigned to dmoluguw
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/3285
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.