Bug #30523
Make Candlepin database migration idempotent
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
Description
The Candlepin database migration happens on every installer run because we cannot reliably detect if there are pending migrations. As a stop gap, we can store the Candlepin RPM in a file and check if it has changed.
Associated revisions
Refs #30523: Let puppet-candlepin handle DB migration workflow
History
#1
Updated by The Foreman Bot over 2 years ago
- Assignee set to Eric Helms
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-candlepin/pull/161 added
#2
Updated by Ewoud Kohl van Wijngaarden over 2 years ago
- Triaged changed from No to Yes
- Target version set to 2.2.0
- Category set to Foreman modules
#3
Updated by Eric Helms over 2 years ago
- Target version changed from 2.2.0 to 2.3.0
#4
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/theforeman/foreman-installer/pull/569 added
#5
Updated by The Foreman Bot over 2 years ago
- Fixed in Releases 2.3.0 added
#6
Updated by Eric Helms over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-candlepin|f32c2e7d9c7326a24a5795714a57bbc18c1e8e33.
Fixes #30523: Create providers to make database migration idempotent