Description of problem:
Local custom yum repositories with Upstream Repository URL file:// is causing foreman-rake katello:upgrades:3.8:clear_checksum_type to fail:
# foreman-rake katello:upgrades:3.8:clear_checksum_type --trace
/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
/usr/share/foreman/lib/tasks/repair_repos_62.rake:2: warning: already initialized constant PULP_IDS_FILE
/usr/share/foreman/lib/tasks/repair_repos.rake:2: warning: previous definition of PULP_IDS_FILE was here
** Invoke katello:upgrades:3.8:clear_checksum_type (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute katello:upgrades:3.8:clear_checksum_type
ActiveRecord::RecordInvalid: Validation failed: Download policy Cannot sync file:// repositories with On Demand or Background Download Policies
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. Have a custom repository with Upstream URL repository pointing to file://
2. Try to upgrade to 6.4.0
3. It fails with above
katello:upgrades:3.8:clear_checksum_type is trying to forcefully set on Demand or Background download policy on locally hosted repos
katello:upgrades:3.8:clear_checksum_type will not try to change download policy on locally hosted yum repositories (Upstream Repository URL file://)
Created redmine issue http://projects.theforeman.org/issues/25968 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25968 has been resolved.
*** Bug 1686798 has been marked as a duplicate of this bug. ***
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.