Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1547607 - satellite-installer --upgrade fails on db:migrate
satellite-installer --upgrade fails on db:migrate
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: SCAP Plugin (Show other bugs)
6.3.0
x86_64 Linux
high Severity high (vote)
: 6.3.1
: Unused
Assigned To: Ondřej Pražák
Sanket Jagtap
: PrioBumpGSS, Triaged, Upgrades
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-21 10:36 EST by Andreas Bleischwitz
Modified: 2018-08-15 09:55 EDT (History)
14 users (show)

See Also:
Fixed In Version: tfm-rubygem-foreman_openscap-0.7.13
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-13 09:32:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
full satellite installer log (148.54 KB, text/plain)
2018-02-21 12:04 EST, Andreas Bleischwitz
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 22668 None None None 2018-02-23 04:08 EST
Red Hat Product Errata RHBA-2018:1126 None None None 2018-04-13 09:33 EDT

  None (edit)
Description Andreas Bleischwitz 2018-02-21 10:36:45 EST
Description of problem:
During the upgrade of Satellite the migration of the database fails and the upgrade is stopped. Any re-start of the upgrade fails with the same error

Version-Release number of selected component (if applicable):

# rpm -q satellite
satellite-6.3.0-23.0.el7sat.noarch


How reproducible:

Update from satellite-6.2.14-4.0.el7sat.noarch.


Actual results:
[ INFO 2018-02-21 16:16:12 main] Upgrade Step: migrate_foreman...
[DEBUG 2018-02-21 16:16:39 main] rake aborted!
[DEBUG 2018-02-21 16:16:39 main] StandardError: An error has occurred, this and all later migrations canceled:
[DEBUG 2018-02-21 16:16:39 main] 
[DEBUG 2018-02-21 16:16:39 main] Failed to destroy the record/opt/rh/rh-ror42/root/usr/share/gems/gems/activerecord-4.2.6/lib/active_record/persistence.rb:185:in `destroy!'
[DEBUG 2018-02-21 16:16:39 main] /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_openscap-0.7.11/db/migrate/20171011134112_remove_arf_reports_without_policy.rb:5:in `map'
[DEBUG 2018-02-21 16:16:39 main] /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_openscap-0.7.11/db/migrate/20171011134112_remove_arf_reports_without_policy.rb:5:in `block in up'
[DEBUG 2018-02-21 16:16:39 main] /opt/rh/rh-ror42/root/usr/share/gems/gems/activerecord-4.2.6/lib/active_record/relation/batches.rb:124:in `find_in_batches'
[DEBUG 2018-02-21 16:16:39 main] /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_openscap-0.7.11/db/migrate/20171011134112_remove_arf_reports_without_policy.rb:4:in `up'
[DEBUG 2018-02-21 16:16:39 main] /opt/rh/rh-ror42/root/usr/share/gems/gems/activerecord-4.2.6/lib/active_record/migration.rb:611:in `exec_migration'


Expected results:
Upgrade finishes without error.

Additional info:
I fixed this issue by removing the "!" from /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_openscap-0.7.11/db/migrate/20171011134112_remove_arf_reports_without_policy.rb:

--- 20171011134112_remove_arf_reports_without_policy.rb-old	2018-02-21 16:19:53.259631092 +0100
+++ 20171011134112_remove_arf_reports_without_policy.rb	2018-02-21 16:22:27.050573034 +0100
@@ -2,7 +2,7 @@
   def up
     ids_to_keep = ForemanOpenscap::ArfReport.unscoped.all.joins(:policy_arf_report).pluck(:id)
     ForemanOpenscap::ArfReport.unscoped.where.not(:id => ids_to_keep).find_in_batches do |batch|
-      batch.map(&:destroy!)
+      batch.map(&:destroy)
     end
   end
 end
Comment 1 Evgeni Golov 2018-02-21 10:44:41 EST
Andreas, do you have the *full* log of the upgrade available?

ActiveRecord::Persistence.destroy! raises an error if the destroy did not work out, ActiveRecord::Persistence.destroy does not, so you basically have hidden the problem ;)
Comment 2 Andreas Bleischwitz 2018-02-21 12:04 EST
Created attachment 1398912 [details]
full satellite installer log
Comment 5 Ondřej Pražák 2018-02-23 04:08:55 EST
Created redmine issue http://projects.theforeman.org/issues/22668 from this bug
Comment 9 pm-sat@redhat.com 2018-02-26 06:03:34 EST
Upstream bug assigned to oprazak@redhat.com
Comment 10 pm-sat@redhat.com 2018-02-26 06:03:39 EST
Upstream bug assigned to oprazak@redhat.com
Comment 16 Sanket Jagtap 2018-04-02 01:30:29 EDT
Build: Satellite 6.3.1 snap1 


Reproducer steps:
1) Have a scap policy 
2) Create a report from the policy 
3) delete the policy 
4) Upgrade your 6.2.14 to 6.3


The upgrade from 6.2.14 to 6.3 was successfully with the orphan arf report in it 
The upgrade successfully remove the orphan arf reports

[qe-sat6-] out: 
[qe-sat6-] out: == 20171011134112 RemoveArfReportsWithoutPolicy: migrating ====================
[qe-sat6-] out: == 20171011134112 RemoveArfReportsWithoutPolicy: migrated (0.0839s) ===========
Comment 18 errata-xmlrpc 2018-04-13 09:32:28 EDT
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:1126

Note You need to log in before you can comment on or make changes to this bug.