Table is missing after a Katello migration from an ancestral version to 3.4 or 3.11

Support
1

Problem:
Impossible to run foreman_rake db:migrate from 3.3 to 3.11 or 3.3
I’ve check on Internet but noone talks about this issue.
I’ve also try to find the database model to build the missing table but once again, I’ve found nothing.

I’ve perhaps done something bad, I’m still able to restore a backup before the migration.

Expected outcome:
Migration successful

Foreman and Proxy versions:
Foreman 3.3, too late to know the old proxy version

Foreman and Proxy plugin versions:
Don’t know

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)

logs

[DEBUG 2019-05-22T11:30:20 main] rake aborted!
[DEBUG 2019-05-22T11:30:20 main] StandardError: An error has occurred, this and all later migrations canceled:
[DEBUG 2019-05-22T11:30:20 main] 
[DEBUG 2019-05-22T11:30:20 main] PG::UndefinedTable: ERROR:  relation "katello_content_facet_applicable_module_streams" does not exist
[DEBUG 2019-05-22T11:30:20 main] LINE 8:                WHERE a.attrelid = '"katello_content_facet_ap...
[DEBUG 2019-05-22T11:30:20 main]                                           ^
[DEBUG 2019-05-22T11:30:20 main] :               SELECT a.attname, format_type(a.atttypid, a.atttypmod),
[DEBUG 2019-05-22T11:30:20 main]                      pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
[DEBUG 2019-05-22T11:30:20 main]                      c.collname, col_description(a.attrelid, a.attnum) AS comment
[DEBUG 2019-05-22T11:30:20 main]                 FROM pg_attribute a
[DEBUG 2019-05-22T11:30:20 main]                 LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
[DEBUG 2019-05-22T11:30:20 main]                 LEFT JOIN pg_type t ON a.atttypid = t.oid
[DEBUG 2019-05-22T11:30:20 main]                 LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation
[DEBUG 2019-05-22T11:30:20 main]                WHERE a.attrelid = '"katello_content_facet_applicable_module_streams"'::regclass
[DEBUG 2019-05-22T11:30:20 main]                  AND a.attnum > 0 AND NOT a.attisdropped
[DEBUG 2019-05-22T11:30:20 main]                ORDER BY a.attnum
[DEBUG 2019-05-22T11:30:20 main] /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:63:in `async_exec'
2

Please read the Katello upgrade release notes for each intermediate version as they describe this scenario.

From 3.3, I think you have to jump to 3.6, then 3.8 update puppet to version 4, then you can go directly to 3.11.

3

Going from 3.3 directly to 3.11, I would expect to see issues like that, that is a quite a leap. The happy path would be to upgrade each incremental version in succession, but the scenario @Tony_Coffman mentions sounds reasonable as well.