Hi,
yesterday Endi told me that the database schema for 10.9.0 is not finalized yet and that the Dogtag team only supports upgrade from GA to GA releases. There are no plans to support migration from 10.9.0 alpha and beta releases. If I understood Endi correctly then alpha and beta releases are not supported.
However 10.9.0-a2 (aka RPM tag 10.9.0-0.2) was build and pushed to Fedora 31 and Fedora 32 stable about a week ago. This means the releases are generally available for Fedora and FreeIPA users. It's too late to yank the releases from Fedora now.
IMO the Dogtag team has to support these versions as well as an upgrade path from the alpha builds to 10.9.0 stable. Otherwise you would break all Fedora users that have installed updates in the past week.
Just to clarify, alpha and beta builds are development builds that are created to facilitate testing prior to releasing the officially supported final (GA) build. The alpha and beta designations indicate that the build may contain incomplete/untested code that might still change prior to the final build (i.e. unstable). The 10.9.0-a2 build was provided into Fedora Bodhi to allow testing with IPA, but it was never meant to be released into Fedora stable. In the future we might add an "unstable" label into the release number to make it more clear (e.g. 10.9.0-0.5.unstable). Stable (i.e. supported) releases will start from <version>-1 (e.g. 10.9.0-1).
As for the upgrade issue, it will have to be evaluated on case-by-case basis. For ACME, the 10.9.0-a2 doc still has a disclaimer about upgradability: https://github.com/dogtagpki/pki/blob/v10.9.0-a2/docs/installation/acme/Installing_ACME_Responder.md Also, IIUC IPA currently doesn't support ACME either, so we may not need to support ACME upgrade from 10.9.0-a2 to GA. In the worst case people might be required to drop and recreate their ACME database manually. I'm not sure about other features/changes in 10.9.0-a2.
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
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/3307
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.