Hi Henrik,
Thanks for your response.
We are not using any environment approach in our master. We are directly using /etc/puppetlabs/puppet/modules and manifests directory and one more thing is we created non root user account to deploy our modules on agents.In non root account configuration we have current for parser value as shown below but while running modules I get syntax errors. Please note we are able to deploy same modules in other environment with out any issues where parser is not present in puppet.conf file.
puppet config print | grep -i parser
parser = current
Environment DEV:
1) We got sudo access to setup master and Agents
2) Copy the modules to master
3) Ran puppet agents with the account which has sudo access
4) Parser value is current and it is not present in puppet.conf file
5) Everything went fin in this environment
Environment TEST
1) We didnt get sudo access due to our policy
2) Admin team setup master and agents and created non root account as per steps in puppet docs
3) We started running puppet agents same as environment DEV and started seeing syntax errors
4) While debugging we understood our modules wont support latest puppet versions and these need to modify to work fine
5) We noticed parser value as future on puppet.conf then we though if we change it then our modules work
4) Removed value parser in puppet.conf and restarted service with the help of admin
5) After restart parser parameter is coming again with the value future and getting same errors while applying modules
Now our question is how can we disable parser value future in our environment ? Do we need to re-install PE? is there any better option in this case for us?
Regards,
Siva