Project

General

Profile

Bug #30523

Make Candlepin database migration idempotent

Added by Eric Helms 3 months ago. Updated 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:

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.

See: https://bugzilla.redhat.com/show_bug.cgi?id=1861868

Associated revisions

Revision f32c2e7d (diff)
Added by Eric Helms 2 months ago

Fixes #30523: Create providers to make database migration idempotent

Revision 34acdc91 (diff)
Added by Eric Helms 2 months ago

Refs #30523: Let puppet-candlepin handle DB migration workflow

History

#1 Updated by The Foreman Bot 3 months 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 3 months ago

  • Triaged changed from No to Yes
  • Target version set to 2.2.0
  • Category set to Foreman modules

#3 Updated by Eric Helms 3 months ago

  • Target version changed from 2.2.0 to 2.3.0

#4 Updated by The Foreman Bot 2 months ago

  • Pull request https://github.com/theforeman/foreman-installer/pull/569 added

#5 Updated by The Foreman Bot 2 months ago

  • Fixed in Releases 2.3.0 added

#6 Updated by Eric Helms 2 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF