Foreman 1.17 RC1 issues

Support
1

I have encountered 2 issues during the upgrade process from 1.16.0 to 1.17 RC1 on RHEL7. First is documentation issue that rake task tmp:sessions:clear is not defined:

[root@foreman-test ~]# foreman-rake tmp:sessions:clear
/opt/theforeman/tfm/root/usr/share/gems/gems/sequel-4.20.0/lib/sequel/database/schema_generator.rb:19: warning: constant ::Fixnum is deprecated
/opt/theforeman/tfm/root/usr/share/gems/gems/sequel-4.20.0/lib/sequel/database/schema_generator.rb:19: warning: constant ::Bignum is deprecated
/usr/share/foreman/lib/core_extensions.rb:183: warning: already initialized constant ActiveSupport::MessageEncryptor::DEFAULT_CIPHER
/opt/rh/tfm-ror51/root/usr/share/gems/gems/activesupport-5.1.4/lib/active_support/message_encryptor.rb:22: warning: previous definition of DEFAULT_CIPHER was here
/opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/appender.rb:139: warning: constant ::Fixnum is deprecated
rake aborted!
Don't know how to build task 'tmp:sessions:clear' (see --tasks)
/opt/rh/rh-ruby24/root/usr/share/gems/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)

The second is that all rake tasks generate warnings:

[root@foreman-test ~]# foreman-rake db:migrate
/opt/theforeman/tfm/root/usr/share/gems/gems/sequel-4.20.0/lib/sequel/database/schema_generator.rb:19: warning: constant ::Fixnum is deprecated
/opt/theforeman/tfm/root/usr/share/gems/gems/sequel-4.20.0/lib/sequel/database/schema_generator.rb:19: warning: constant ::Bignum is deprecated
/usr/share/foreman/lib/core_extensions.rb:183: warning: already initialized constant ActiveSupport::MessageEncryptor::DEFAULT_CIPHER
/opt/rh/tfm-ror51/root/usr/share/gems/gems/activesupport-5.1.4/lib/active_support/message_encryptor.rb:22: warning: previous definition of DEFAULT_CIPHER was here
/opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/appender.rb:139: warning: constant ::Fixnum is deprecated
/opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/logger.rb:295: warning: constant ::Fixnum is deprecated

Do both warrant separate issues?

1 Like
2

Hi,
the deprecation warnings come mostly from other gems, they will be gone when we move to newer versions. The missing rake task is a valid documentation issue.

O.

3

We could tag in logging 2.2.2 which we have in nightly. It doesn’t have the deprecation warnings under Ruby 2.4. http://koji.katello.org/koji/buildinfo?buildID=23415

We could also update sequel but haven’t done that in nightly yet. We’ve had some reports from Debian (which includes a newer version) with issues so I’m a bit more hesitant to just update it to the newest. See https://projects.theforeman.org/issues/20050#note-14