Bug #34308
Seed may not be triggered after migration
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
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.
Associated revisions
History
#1
Updated by The Foreman Bot 10 months ago
Updated by - Assignee set to Ewoud Kohl van Wijngaarden
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman/pull/1020 added
#2
Updated by The Foreman Bot 10 months ago
- Fixed in Releases 3.2.0 added
#3
Updated by Ewoud Kohl van Wijngaarden 10 months ago
Updated by - Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman|d86ea26f7ac50cd708c17b9333a88f1bbadbf3d9.
#4
Updated by Ewoud Kohl van Wijngaarden 10 months ago
- Triaged changed from No to Yes
- Fixed in Releases 3.1.1 added
Fixes #34308 - Explicitly notify db:seed from db:migrate
This is similar to a293e0084d3c2d62c12ccc6a13338b5db01fe8cf and the
problem is that a transitive notify doesn't always happen. However, if
a db:migrate happens a db:seed should always happen. So his may be a
redundant specification, but it's better to be explicit than relying on
implicit behavior.