Plugins » foreman-tasks

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1853200

Description of problem: foreman-rake-db:migrate command return 1 instead of 0 while upgrading the satellite from 6.7 to 6.8.

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

How reproducible:
always

Steps to Reproduce:
1. Prepare the environment to perform the satellite-upgrade from 6.7 to 6.8
2. Configure the all required repository to perform the upgrade from 6.7 to 6.8.
3. Apply the workaround mentioned on BZ#1846593#c5
4: Run foreman-maintain upgrade check and it completes with some expected warning messages.

5: Run foreman upgrade using below command

foreman-maintain upgrade run --whitelist="disk-performance, repositories-validate, repositories-setup" --target-version 6.8 -y

Running Migration scripts to Satellite 6.8

===========================================================================
 Setup repositories:                                                   [SKIPPED]
 ------------------------------------------------------------------------------
 Unlock packages:                                                      [OK]
 ------------------------------------------------------------------------------

Update package(s) :                                                   [OK]
 ------------------------------------------------------------------------------

Procedures::Installer::Upgrade:                                       [FAIL]
 Failed executing LANG=en_US.utf-8 satellite-installer, exit status 6:

Hook /usr/share/foreman-installer/katello/hooks/post/99-version_locking.rb returned true
All hooks in group post finished
Exit with status code: 6 (signal was 6)
Errors encountered during run:
'/usr/sbin/foreman-rake db:migrate' returned 1 instead of one of [0]
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/errors.rb:157:in `fail'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/exec.rb:183:in `sync'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:241:in `sync'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:136:in `sync_if_needed'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:90:in `block in perform_changes'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:89:in `each'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:89:in `perform_changes'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:21:in `evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:267:in `apply'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:287:in `eval_resource'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:191:in `call'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:191:in `block (2 levels) in evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:521:in `block in thinmark'
/opt/puppetlabs/puppet/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:520:in `thinmark'

Actual results:
foreman-rake-db:migrate return 1 instead of 0

Expected results:
foreman-rake-db:migrate should be completed successfully.

Additional info: