Project

General

Profile

Actions

Bug #34308

closed

Seed may not be triggered after migration

Added by Ewoud Kohl van Wijngaarden about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

In puppet-foreman we rely on a transitive notification from foreman::rake db:migrate via foreman_config_entry db_pending_seed to foreman::rake db:seed. In #34161 we've seen that this isn't always true. An explicit notification would be better.

Actions #1

Updated by The Foreman Bot about 2 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ewoud Kohl van Wijngaarden
  • Pull request https://github.com/theforeman/puppet-foreman/pull/1020 added
Actions #2

Updated by The Foreman Bot about 2 years ago

  • Fixed in Releases 3.2.0 added
Actions #3

Updated by Ewoud Kohl van Wijngaarden about 2 years ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by Ewoud Kohl van Wijngaarden about 2 years ago

  • Triaged changed from No to Yes
  • Fixed in Releases 3.1.1 added
Actions

Also available in: Atom PDF