Project

General

Profile

Bug #25125

Rename migrations timestamp to avoid collision

Added by Daniel Lobato Garcia 11 months ago. Updated 11 months ago.

Status:
Ready For Testing
Priority:
Normal
Category:
DB migrations
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

#25102 was merged recently and it contains a number of migrations with the exact same timestamp as some previously existing migrations in REX.

This causes an error when you upgrade a system where REX was installed before (db:migrate):

ActiveRecord::DuplicateMigrationVersionError:

Multiple migrations have the version number 20150616080015.

I can't see a reason why this wouldn't happen on production too during an upgrade, even if we remove the migrations from REX, the timestamps are still saved in memory.


Related issues

Related to Foreman - Feature #25102: Formalize template inputsClosed

History

#1 Updated by Daniel Lobato Garcia 11 months ago

#2 Updated by The Foreman Bot 11 months ago

  • Assignee set to Daniel Lobato Garcia
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6111 added

Also available in: Atom PDF