DB migrate and seed should be re-run if an error occurred during the run of either
Refs #4611 - rake-ify foreman-config and db_pending_migration/seed in settings
This way, we can determine in the installer if the rake
db:migrate/seed should be run in the installer.
Later, we also could use this information to inform the entering user
that the application is not in ready state yet: preparation for
This allows tracking the state of migration/seeding in the database
and making sure the rake tasks are done on subsequential installer attempts when
something goes wrong the first time.
Also, as part of the `foreman-config` calls, we ensure that the
settings are initialised before the httpd starts (preventing the
race-conditions happening when the httpd and rake db:seed start at the
#7 Updated by Ivan Necas about 5 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset puppet-foreman|dcde67122d8151e16b905201196a764671f0d63d.