Remove warning messages when running console to improve user experience when debugging issues: [root@sat foreman]# foreman-rake console /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_theme_satellite-0.1.41/app/models/concerns/satellite_packages.rb:4: warning: already initialized constant Katello::Ping::PACKAGES /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.105/app/models/katello/ping.rb:7: warning: previous definition of PACKAGES was here /usr/share/foreman/lib/tasks/console.rake:4: warning: already initialized constant ARGV Loading production environment (Rails 4.1.5) irb(main):001:0> Please also fix the console.rake (4) error if possible.
We are tracking the Katello::Ping::PACKAGES in https://bugzilla.redhat.com/show_bug.cgi?id=1429418. I'm keeping this bug opened for the `warning: already initialized constant ARGV`
Created redmine issue http://projects.theforeman.org/issues/19241 from this bug
Fix proposed at https://github.com/theforeman/foreman/pull/4450
Upstream bug assigned to inecas
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19241 has been resolved.
Verified. Version Tested: Satellite-6.3 Snap 9. rake-console output screen-shots attached. ** RPM package versions: satellite-6.3.0-16.0.beta.el7sat.noarch foreman-1.15.2-1.el7sat.noarch katello-3.4.2-1.el7sat.noarch tfm-rubygem-hammer_cli-0.10.2-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman-0.10.2-1.el7sat.noarch Resolved -> `warning: already initialized constant ARGV` is not showing on sat 6.3. *** New Bug *** warning message related to redhat-access is showing up when running console. Created new BZ[https://bugzilla.redhat.com/show_bug.cgi?id=1479720] [root@sat63-qa-rhel7 ~]# foreman-rake console /opt/theforeman/tfm/root/usr/share/gems/gems/redhat_access-2.0.3/app/services/redhat_access/telemetry/look_ups.rb:171: warning: key :hosts is duplicated and overwritten on line 172 Loading production environment (Rails 4.2.6) Failed to load console gems, starting anyway irb(main):001:0> exit
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:0336