Warning messages in production.log

Support
1

Bonjour,

Sorry if this is an old problem but I am unable to find any information.

I am trying to upgrade from 2.5.4 to 3.0.1 and get some warning with both versions (I think they were present in older version but I have never checked before)

First warning occurs when I do a puppet agent -t (or when the puppet service runs)
The report parameter was renamed to config_reports and the API endpoint has changed from /reports to /config_reports. Please use the new API.

And I get the second warning when I open the dashboard Setting all_out_of_sync_disabled has no definition, please define it before using

How can I fix those warnings ?

Thank you for your help

Regards,

Frederic

2

Hello and welcome!

The endpoint was renamed in Refactor #28594: drop reports api endpoint - Foreman but I am not sure why are you still running into this. Perhaps an old proxy version or old configuration (ENC.rb)? @ekohl any ideas?

This looks like you have some value in settings.yaml which is no longer supported, not sure. @ezr-ondrej any idea?

3

[lzap] lzap Core
January 10

Hello and welcome!

Thank you for your answer

I have just installed a new server (centos7 / foreman 2.5.4 like my
production server)
using this guide (
Installing Foreman 2.5 server on Enterprise Linux )

frederic:

The report parameter was renamed to config_reports and the API
endpoint has changed from /reports to /config_reports. Please use
the new API.

The endpoint was renamed in Refactor #28594: drop reports api endpoint

  • Foreman but I am not sure why are you still running into this.
    Perhaps an old proxy version or old configuration (ENC.rb)? @ekohl any
    ideas?

the files are identical on the fresh install and the production

( /usr/share/foreman-installer/modules/puppetserver_foreman/files/enc.rb and
/usr/share/foreman-installer/modules/foreman/lib/puppet/functions/foreman/enc.rb
)

frederic:

And I get the second warning when I open the dashboard *Setting
all_out_of_sync_disabled has no definition, please define it
before using*

This looks like you have some value in |settings.yaml| which is no
longer supported, not sure. @ezr-ondrej any idea?

The warning is also present in the fresh install :frowning:

Visit Topicor reply to this email to respond.

To unsubscribe from these emails, click here.

Thank you

Regards,

Frederic

4

This is harmless, it is warning about reading a setting that doesn’t exists. That was always happening, but we’ve introduced a warning message so we know about such cases. Thanks for reporting! :slight_smile:

I’ve filed an issue for that Bug #34240: Setting all_out_of_sync_disabled has no definition warning - Foreman and filed a PR fixing it[1]. If you want, you may patch your instance to get rid of the warning. If you let us know if that helped, it would be appreciated :slight_smile:

[1] Fixes #34240 - do not read undefined setting by ezr-ondrej · Pull Request #9024 · theforeman/foreman · GitHub

5

I apply the patch but the message is still there.

Is there any command to run after editing the file (I run
foreman-installer just in case) ?

Thank you for your help

Regards,

Frederic

6

I think foreman-installer will reset the file to the original (not sure about that). You should restart the foreman service after editing the file (not sure if it’s also called foreman on Debian tho).

7

After resetting foreman, your patch works

Sorry I thought foreman-installer will restart everything (but it does
not change the file)

Thank you very much

Regards,

Frederic

Frédéric AYRAULT
Administrateur Systèmes et Réseaux
Laboratoire d’Informatique de l’Ecole polytechnique
http://www.lix.polytechnique.fr
fred@lix.polytechnique.fr

alonklfijbnemonl.png

2 Likes
8

For the first warning (The report parameter was renamed to config_reports and the API endpoint has changed from /reports to /config_reports. Please use the new API.)

I found old backups (end of 2020 and start of 2021)

I did not have the message when the server was runing 1.24.3 but it is present in 2.2.2

Maybe I forgot something or made a mistake in the upgrade to version 2.

This warning is quite old and foreman work very well but maybe someone will remember
how to get rid of it :crossed_fingers:

Thank you

Regards,

Frederic

1 Like