This is from https://github.com/theforeman/foreman_templates/issues/101 I just upgraded a test system to 1.18 RC3 and foreman_templates 6.0.2 and am getting an error running the rake task for import: <pre> [root@foreman-test ~]# foreman-rake templates:import /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 rake aborted! ArgumentError: wrong number of arguments (given 1, expected 0) /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_templates-6.0.2/lib/tasks/foreman_templates_tasks.rake:34:in `to_h' /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_templates-6.0.2/lib/tasks/foreman_templates_tasks.rake:34:in `block (3 levels) in <top (required)>' /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_templates-6.0.2/lib/tasks/foreman_templates_tasks.rake:34:in `each' /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_templates-6.0.2/lib/tasks/foreman_templates_tasks.rake:34:in `map' /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_templates-6.0.2/lib/tasks/foreman_templates_tasks.rake:34:in `block (2 levels) in <top (required)>' /opt/rh/rh-ruby24/root/usr/share/gems/gems/rake-12.0.0/exe/rake:27:in `<top (required)>' Tasks: TOP => templates:import (See full trace by running task with --trace) </pre>
Created from redmine issue https://projects.theforeman.org/issues/24208
Upstream bug assigned to oprazak
reproducing steps: try running foreman-rake templates:import actual results: fails with the error above expects results: works fine and prints results while this is discouraged and deprecated way of triggering import, it should still work
Verified: @satellite 6.4.0 snap 16 @ tfm-rubygem-foreman_templates-6.0.3-1.el7sat.noarch steps: #foreman-rake templates:import Observation: - works fine and prints results - No error occured
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/RHSA-2018:2927