#2947 pki-server migrate CLI improvements
Closed: fixed 6 years ago Opened 6 years ago by edewata.

The pki-server migrate is a script that handles Tomcat 7.0 to 8.0 migration. The migration is always executed regardless of version number.

Currently the script is executed during RPM upgrade for all instances. It needs to be moved into system unit file so that the migration is executed only on the instance being started. Right now the script does not accept an instance name param, so that will need to be fixed first.

Supposedly the code that does NSS DBM to SQL migration could be moved into this script. Also, the Tomcat 8.0 to 8.5 migration will need to be done in this script as well.


For now, DBM to SQL migration is handled by a hack in pki-server-upgrade. It's always triggered as first action to ensure that NSSDB has correct format. The hack can be removed when migration has been moved into pki-server migrate.

See https://review.gerrithub.io/c/401067/

Metadata Update from @cheimes:
- 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

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

6 years ago

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue close_status updated to: fixed
- Issue priority set to: critical
- Issue set to the milestone: 10.6.0 (was: 0.0 NEEDS_TRIAGE)
- Issue status updated to: Closed (was: Open)

6 years ago

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/3065

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata