Description of problem: When upgrading from 6.2 to 6.3 the content_source_id parameter from hosts is moved from the hosts table to the katello_content_facets table. As seen in the satellite.log form an upgrade here: --- -- add_column(:katello_content_facets, :content_source_id, :integer) -- add_index(:katello_content_facets, :content_source_id) -- add_foreign_key(:katello_content_facets, :smart_proxies, {:name=>"katello_content_facets_content_source_id_fk", :column=>"content_source_id"}) -- remove_foreign_key(:hosts, {:name=>"hosts_content_source_id_fk"}) -- remove_index(:hosts, :content_source_id) -- remove_column(:hosts, :content_source_id) --- The problem here is that it doesn't appear that the value set for the content_source_id parameter in the hosts table is migrated to the katello_content_facets table when the new column is created. All values in the new column are blank. For example: === 6.2.14 (before upgrade) foreman=# select count(id) from hosts where content_source_id is null; count ------- 24 (1 row) foreman=# select count(id) from hosts where content_source_id is not null; count ------- 105 (1 row) === 6.3.1 (after upgrade) foreman=# select count(id) from katello_content_facets where content_source_id is null; count ------- 117 (1 row) foreman=# select count(id) from katello_content_facets where content_source_id is not null; count ------- 0 (1 row) === Actual results: Table values are not migrated Expected results: Table values are migrated and kept
Created redmine issue http://projects.theforeman.org/issues/23781 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23781 has been resolved.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1950