Foreman » Installer

I assume this is because db:migrate / seed only happens during package post?

Ohad Levy wrote:

I assume this is because db:migrate / seed only happens during package post?

That's only the case in a package-only installation. When using the installer, DB configuration happens after package installation, so the installer runs migrations/seeding itself.

Here is the output of running foreman-config manually and a full foreman-debug was uploaded (foreman-debug-bhzqA.tar.xz):

[root@katello-foreman share]# su - foreman -s /bin/bash -c "/usr/share/foreman/script/foreman-config -k 'db_pending_migration'" 
foreman-config script is deprecated. Please consider using `foreman-rake config` instead
foreman_bootdisk: skipping engine hook (PGError: ERROR:  relation "template_kinds" does not exist
LINE 4:              WHERE a.attrelid = '"template_kinds"'::regclass
                                        ^
:             SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull
              FROM pg_attribute a LEFT JOIN pg_attrdef d
                ON a.attrelid = d.adrelid AND a.attnum = d.adnum
             WHERE a.attrelid = '"template_kinds"'::regclass
               AND a.attnum > 0 AND NOT a.attisdropped
             ORDER BY a.attnum
)
rake aborted!
PGError: ERROR:  relation "settings" does not exist
LINE 4:              WHERE a.attrelid = '"settings"'::regclass
                                        ^
:             SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull
              FROM pg_attribute a LEFT JOIN pg_attrdef d
                ON a.attrelid = d.adrelid AND a.attnum = d.adnum
             WHERE a.attrelid = '"settings"'::regclass
               AND a.attnum > 0 AND NOT a.attisdropped
             ORDER BY a.attnum

Tasks: TOP => config
(See full trace by running task with --trace)
[root@katello-foreman share]# echo $?
1

Something like this is what I thought for my last comment:

    class { $db_class: } ->
    foreman_config_entry { 'db_pending_migration':
      value          => false,
      dry            => true,
      ignore_missing => true,
    } ~>
    foreman::rake { 'db:migrate':
      subscribe => Class[$db_class],      ## added this line
    } ->
    foreman_config_entry { 'db_pending_seed':
      value          => false,
      dry            => true,
      ignore_missing => true,
      # to address #7353: settings initialization race condition
      before         => $foreman_service,
    } ~>
    foreman::rake { 'db:seed':
# .....

That retains 1.6 compatibility - although 'master' doesn't require it, then any change to the "db_class" (foreman::db::postgresql) will always trigger a migration, just in case.