Description of problem: z-stream upgrade i.e. 6.4.0 to 6.4.1 upgrade failed at <trimmed> Upgrade Step: migrate_foreman... /usr/share/foreman/lib/foreman.rb:8: warning: already initialized constant Foreman::UUID_REGEXP /usr/share/foreman/lib/foreman.rb:8: warning: previous definition of UUID_REGEXP was here /usr/share/foreman/lib/core_extensions.rb:182: warning: already initialized constant ActiveSupport::MessageEncryptor::DEFAULT_CIPHER /opt/theforeman/tfm-ror51/root/usr/share/gems/gems/activesupport-5.1.6/lib/active_support/message_encryptor.rb:22: warning: previous definition of DEFAULT_CIPHER was here API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache. /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.7.0.42/app/models/katello/concerns/content_facet_host_extensions.rb:7: warning: already initialized constant Katello::Concerns::ContentFacetHostExtensions::ERRATA_STATUS_MAP /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.7.0.42/app/models/katello/concerns/content_facet_host_extensions.rb:7: warning: previous definition of ERRATA_STATUS_MAP was here /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.7.0.42/app/models/katello/concerns/content_facet_host_extensions.rb:14: warning: already initialized constant Katello::Concerns::ContentFacetHostExtensions::TRACE_STATUS_MAP /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.7.0.42/app/models/katello/concerns/content_facet_host_extensions.rb:14: warning: previous definition of TRACE_STATUS_MAP was here /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.7.0.42/app/models/katello/concerns/subscription_facet_host_extensions.rb:13: warning: already initialized constant Katello::Concerns::SubscriptionFacetHostExtensions::SUBSCRIPTION_STATUS_MAP /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.7.0.42/app/models/katello/concerns/subscription_facet_host_extensions.rb:13: warning: previous definition of SUBSCRIPTION_STATUS_MAP was here foreman-rake db:migrate finished successfully! Upgrade Step: remove_legacy_mongo... Upgrade step remove_legacy_mongo failed. Check logs for more information. Version-Release number of selected component (if applicable): Upgrade from 6.4.0 to 6.4.1 How reproducible: always Steps to Reproduce: 1. foreman-maintain upgrade run --target-version 6.4.z -y Actual results: Upgrade failed at Upgrade Step: remove_legacy_mongo Expected results: Successful upgrade. Additional info:
Regression from https://bugzilla.redhat.com/show_bug.cgi?id=1646741
Nikhil, The bug you attached that you stated this is a regression from is also on 6.4.1 snap 1, shouldn't that bug be FailedQA instead of creating a new regression?
Hi Patrick, I raised this to track issue separately as both the scenarios need to validate while testing/verifying. If you want, feel free to close this duplicate and failedQA another bug with comment to verify z-stream upgrade as well. I am ok with that.
Ah, ok. I didn't pick up on that z-stream nuance. Sounds good to me, apologies for the nosie
VERIFIED Version tested: Satellite 6.4.1 snap 2 Upgrade from 6.4.0 to 6.4.1 is successful. foreman-rake db:migrate finished successfully! Upgrade Step: remove_legacy_mongo... Upgrade Step: Running installer... Preparing installation Debug: Loading facts from /usr/share/foreman-insta[[KPreparing installation Info: Facter: loading custom facts from /usr/share[[KPreparing installation Debug: Facter: searching for
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:3799