Description of problem: when upgrading to satellite 6.2 from 6.1.9 we received openscap error in the satellite.log Version-Release number of selected component (if applicable): How reproducible: have not reproduced. pre health check script passed before upgrade. Steps to Reproduce: 1. 2. 3. Actual results: db:migrate 18195 (See full trace by running task with --trace) 18196 == 20150612135546 CreateHostStatus: migrating ================================= 18197 -- create_table(:host_status) 18198 -> 0.0412s 18199 -- add_index(:host_status, :host_id) 18200 -> 0.0051s 18201 -- add_foreign_key("host_status", "hosts", {:name=>"host_status_hosts_host_id_fk", :column=>"host_id"}) 18202 -> 0.0044s 18203 -- add_column(:hosts, :global_status, :integer, {:default=>0, :null=>false}) Expected results: a completed satellite upgrade or the health check for hosts to fail before upgrade. We did delete the host out of the webui, and it did not get us passed this error. Additional info: adding full satellite.log
Created redmine issue http://projects.theforeman.org/issues/16485 from this bug
Upstream bug assigned to mhulan
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16485 has been resolved.
*** Bug 1386524 has been marked as a duplicate of this bug. ***
Marek: can you get QE some guidelines on how to test this during an upgrade?
If the bug was present, it would fail on upgrade during rake db:migrate. So in order to test it is fixed, make sure you have Satellite 6.1, make sure some host has at least one openscap report, try upgrading to 6.2 where host statuses were introduced.
Build: Satellite 6.2.10 snap2 1) Satellite 6.1 (hosts+reports) 2) Perfromed upgrade from 6.1 to 6.2.10 snap2 Upgrade was successful PFA, Upgrade Step: migrate_foreman...
Created attachment 1283828 [details] Migrate_foreman
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-2017:1553