Bug 1274915 - Cannot start pki-ca after upgrade
Cannot start pki-ca after upgrade
Product: Fedora
Classification: Fedora
Component: pki-core (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Matthew Harmsen
Fedora Extras Quality Assurance
Depends On:
Blocks: 1274905
  Show dependency treegraph
Reported: 2015-10-23 16:20 EDT by Martin Kosek
Modified: 2016-12-20 10:07 EST (History)
4 users (show)

See Also:
Fixed In Version: pki-core-10.2.6-12.fc23
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 10:07:43 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
PKI service status after upgrade (14.38 KB, text/plain)
2015-10-23 16:22 EDT, Martin Kosek
no flags Details

  None (edit)
Description Martin Kosek 2015-10-23 16:20:56 EDT
Description of problem:
I upgraded FreeIPA (and PKI) to Fedora 23, but the upgrade crashed when trying to start the CA. Since then, I cannot start the CA, it is complaining about JARs. Please see included systemctl logs.

Version-Release number of selected component (if applicable):

How reproducible:
One time

Steps to Reproduce:
1. Install Freeipa on F22
2. Upgrade to F23

Actual results:
Upgrade fails as PKI cannot be started during the upgrade

Expected results:

Additional info:
Comment 1 Martin Kosek 2015-10-23 16:22 EDT
Created attachment 1085930 [details]
PKI service status after upgrade
Comment 2 Endi Sukma Dewata 2015-10-24 11:21:54 EDT
Currently the Tomcat migration needs to be done manually:
$ pki-server migrate --tomcat 8

See also: https://fedorahosted.org/pki/ticket/1310

If this ticket needs an earlier milestone or a higher priority please indicate so in the ticket. Thanks.
Comment 3 Martin Kosek 2015-10-26 05:01:13 EDT
Thank's Endi, that fixed the problem on my F23.

Looking at the ticket, 10.4 is too far release, this needs to be fixed in Fedora 23, even if at least as 0day update so that upgrades to Fedora 23 succeed.
Comment 4 Endi Sukma Dewata 2015-11-02 11:53:36 EST
Added automatic Tomcat migration:
* master: c7bc6eb94aa64c89467f9394554f860dc485ad94 

Fixed in pki-core-10.2.6-12.fc23: ​https://bodhi.fedoraproject.org/updates/FEDORA-2015-f12c332a2f
Comment 5 Fedora End Of Life 2016-11-24 07:53:30 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2016-12-20 10:07:43 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.