Bug #23781
closedcontent_source_id value is not migrated during upgrade
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1584874
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
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Stephen Benjamin
- Pull request https://github.com/Katello/katello/pull/7413 added
Updated by Stephen Benjamin over 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|ced737abf2752cda53da2149cb02dbecb8277cd9.
Updated by John Mitsch over 6 years ago
- Subject changed from content_source_id value is not migrated during upgrade to content_source_id value is not migrated during upgrade
- Translation missing: en.field_release set to 338
Updated by Stephen Benjamin over 6 years ago
- Related to Bug #23841: hosts table still contains content_view_id and lifecycle_environment_id added