-
Notifications
You must be signed in to change notification settings - Fork 23
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Is this a critical security issue?
- This is not a security issue.
Describe the Bug
Hi, we migrate from puppet 7.34 to openvox 8.22. Two weeks ago
But we have a strange behavior.
puppet agent -t =>works fine
puppet agent -t --environment plop => which is a clone of the production branch return several changement in /opt/puppetlabs/puppet/cache/lib/puppet and /opt/puppetlabs/puppet/cache/lib/puppet_x/
After the migration we update some old plugin, like the latest mysql module.
Expected Behavior
No change between the branch, and get the same module version
Steps to Reproduce
We got error on the plop branch, related to this module, but not in the production branch, but the code is the same at 100%.
Here my puppet.conf
[server]
vardir = /opt/puppetlabs/server/data/puppetserver
logdir = /var/log/puppetlabs/puppetserver
rundir = /var/run/puppetlabs/puppetserver
pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
codedir = /etc/puppetlabs/code
autosign = true
[main]
server = xxxxxx-standalone-l1.in.xxxx.fr
basemodulepath = /etc/puppetlabs/code/environments/production/site-modules:/etc/puppetlabs/code/environments/production/modules
runinterval = 2h
reportdir = /centralelille/puppet/reports
reports = puppetdb
storeconfigs = true
storeconfigs_backend = puppetdb
And the environment.conf on my production branch, i think the problem is here :
modulepath = site:modules:vendor
manifest = manifests/site.pp
Environment
Openvox 8.22 on Debian 12
Additional Context
No response
Relevant log output
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working