Foreman-rake issue in foreman puppet module?

Support
1

Good day,
We are using the foreman puppet module to build out additional foreman
servers.
Every agent run the report shows applied 2 restarted 8.
When you look at the report it states:

/Stage[main]/Foreman::Database/Foreman_config_entry[db_pending_migration]/value value
changed 'Successfully encrypted field for Setting::Auth oauth_consumer_key
Successfully decrypted field for Setting::Auth oauth_consumer_key
Successfully decrypted field for Setting::Auth oauth_consumer_key
Successfully decrypted field for Setting::Auth oauth_consumer_key
Successfully encrypted field for Setting::Auth oauth_consumer_secret
Successfully decrypted field for Setting::Auth oauth_consumer_secret
Successfully decrypted field for Setting::Auth oauth_consumer_secret
Successfully decrypted field for Setting::Auth oauth_consumer_secret
false' to 'false'

notice
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate] Triggered
'refresh' from 1 events
notice
/Stage[main]/Foreman::Database/Foreman_config_entry[db_pending_seed]/value value
changed 'Successfully encrypted field for Setting::Auth oauth_consumer_key
Successfully decrypted field for Setting::Auth oauth_consumer_key
Successfully decrypted field for Setting::Auth oauth_consumer_key
Successfully decrypted field for Setting::Auth oauth_consumer_key
Successfully encrypted field for Setting::Auth oauth_consumer_secret
Successfully decrypted field for Setting::Auth oauth_consumer_secret
Successfully decrypted field for Setting::Auth oauth_consumer_secret
Successfully decrypted field for Setting::Auth oauth_consumer_secret
false' to 'false'

notice
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed] Triggered
'refresh' from 1 events
notice
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache:index]/Exec[foreman-rake-apipie:cache:index] Triggered
'refresh' from 1 events
notice
/Stage[main]/Foreman::Plugin::Memcache/Foreman::Plugin[memcache]/Package[tfm-rubygem-foreman_memcache] Triggered
'refresh' from 1 events
notice /Stage[main]/Foreman::Service/Anchor[foreman::service_begin] Triggered
'refresh' from 1 events
notice /Stage[main]/Foreman::Service/Anchor[foreman::service_end] Triggered
'refresh' from 1 events
notice /Stage[main]/Foreman::Service/Exec[restart_foreman] Triggered
'refresh' from 1 events
notice /Stage[main]/Foreman::Service/Service[foreman]/ensure ensure changed
'running' to 'stopped'
notice /Stage[main]/Foreman::Service/Service[foreman] Triggered 'refresh'
from 1 events

If we run the foreman-rake db:migrate command from the shell same results.

Does anyone have a suggestion as to what may be causing this or how we can
correct it?

Thank you

2

It appears this is a known bug currently open.

http://projects.theforeman.org/issues/18200

Hope this helps others.

··· On Wednesday, May 24, 2017 at 6:25:05 AM UTC-5, Jason McMahan wrote: > > Good day, > We are using the foreman puppet module to build out additional foreman > servers. > Every agent run the report shows applied 2 restarted 8. > When you look at the report it states: > > > /Stage[main]/Foreman::Database/Foreman_config_entry[db_pending_migration]/value value > changed 'Successfully encrypted field for Setting::Auth oauth_consumer_key > Successfully decrypted field for Setting::Auth oauth_consumer_key > Successfully decrypted field for Setting::Auth oauth_consumer_key > Successfully decrypted field for Setting::Auth oauth_consumer_key > Successfully encrypted field for Setting::Auth oauth_consumer_secret > Successfully decrypted field for Setting::Auth oauth_consumer_secret > Successfully decrypted field for Setting::Auth oauth_consumer_secret > Successfully decrypted field for Setting::Auth oauth_consumer_secret > false' to 'false' > > notice > /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate] Triggered > 'refresh' from 1 events > notice > /Stage[main]/Foreman::Database/Foreman_config_entry[db_pending_seed]/value value > changed 'Successfully encrypted field for Setting::Auth oauth_consumer_key > Successfully decrypted field for Setting::Auth oauth_consumer_key > Successfully decrypted field for Setting::Auth oauth_consumer_key > Successfully decrypted field for Setting::Auth oauth_consumer_key > Successfully encrypted field for Setting::Auth oauth_consumer_secret > Successfully decrypted field for Setting::Auth oauth_consumer_secret > Successfully decrypted field for Setting::Auth oauth_consumer_secret > Successfully decrypted field for Setting::Auth oauth_consumer_secret > false' to 'false' > > notice > /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed] Triggered > 'refresh' from 1 events > notice > /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache:index]/Exec[foreman-rake-apipie:cache:index] Triggered > 'refresh' from 1 events > notice > /Stage[main]/Foreman::Plugin::Memcache/Foreman::Plugin[memcache]/Package[tfm-rubygem-foreman_memcache] Triggered > 'refresh' from 1 events > notice /Stage[main]/Foreman::Service/Anchor[foreman::service_begin] Triggered > 'refresh' from 1 events > notice /Stage[main]/Foreman::Service/Anchor[foreman::service_end] Triggered > 'refresh' from 1 events > notice /Stage[main]/Foreman::Service/Exec[restart_foreman] Triggered > 'refresh' from 1 events > notice /Stage[main]/Foreman::Service/Service[foreman]/ensure ensure > changed 'running' to 'stopped' > notice /Stage[main]/Foreman::Service/Service[foreman] Triggered 'refresh' > from 1 events > > If we run the foreman-rake db:migrate command from the shell same results. > > Does anyone have a suggestion as to what may be causing this or how we can > correct it? > > Thank you >
3

This bug is specifically about audit entries, not logging.

#19534 reduces the encryption-related logging which may be affecting the
provider.

··· On 25/05/17 12:31, Jason McMahan wrote: > It appears this is a known bug currently open. > > http://projects.theforeman.org/issues/18200

–
Dominic Cleal
dominic@cleal.org