Current FreeIPA upgrade method has several major drawbacks:
The new joint upgrade tool should solve this and other biggest pain points of the updater. It should also start storing the current version of the data/configuration it updated to, so that by default it is not run several times when the version is the same. It should also not allow running newer data/configuration on older version of the bits.
Sub-parts: #4834, #3560, #3351, #3849
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1199520
master:
A Dogtag ticket https://fedorahosted.org/pki/ticket/1348 was now filed to make one-stop upgrades of Dogtag possible and easy.
Should ipa-server-upgrade call pki-server-upgrade?
Replying to [comment:8 adelton]:
A Dogtag ticket https://fedorahosted.org/pki/ticket/1348 was now filed to make one-stop upgrades of Dogtag possible and easy. Should ipa-server-upgrade call pki-server-upgrade?
Tracked in #4996
IPA probably should call pki-server-migrate to switch to a different platform (see the Dogtag ticket).
Metadata Update from @mkosek: - Issue assigned to mbasti - Issue set to the milestone: FreeIPA 4.2
Login to comment on this ticket.