voxpupuli/container-puppetserver

Puppet 8 container needs to be restarted to register configuraiton changes in Gitlab

Opened this issue · 3 comments

timur-enet commented

Hello, we have recently upgraded Puppet from version 7 to 8 and we have encountered the following issue:

We use a containerized version of Puppet in conjunction with Gitlab where we store configuration data. Before upgrading to v8 the Puppet server used to acknowledge changes in Gitlab automatically (after performing a git pull via cron job)

Since we upgraded to v8 we have to restart the Puppet container in order for the managed systems to recieve the upgraded configuration.

We can not find any issues or irregularities in the log files and we do not know how to proceed. We are using docker image voxpupuli/container-puppetserver:main-8

Please let me know what additional information you need to diagnose the issue.
Kind Regards
Timur

anders-larsson commented

Hello,

environment_timeout = unlimited was recently set. This means the environment will be cached until the service is restarted or the administrative API used to reset it1. You can change the behaviour with environment variable PUPPETSERVER_ENVIRONMENT_TIMEOUT.

  • 👍1
rwaffen commented

@timur-enet did you try the hint from @anders-larsson about the PUPPETSERVER_ENVIRONMENT_TIMEOUT ? Did it work for you?

jwenjian commented

I have similar issues before., set PUPPETSERVER_ENVIRONMENT_TIMEOUT to 0 works for me

  • 👍1