Unknown variable: 'chrony::ptpport' compilation error only when requested environment doesn't exist and falling back to default

[barney-garrett]

We have a stranage behaviour that we are only noticing when the agent is run against an environment that no longer exists on the server and the run falls back to the default environment (in our case called production)

# puppet agent -t --environment rubbish
Info: Refreshing CA certificate
Info: CA certificate is unmodified, using existing CA certificate
Info: Refreshing CRL
Info: CRL is unmodified, using existing CRL
Info: Using environment 'rubbish'
Notice: Environment 'rubbish' not found on server, skipping initial pluginsync.
Info: Loading facts
Notice: Requesting catalog from ccs01:8140 (198.61.86.77)
Notice: Catalog compiled by ccs01
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Unknown variable: 'chrony::ptpport'. (file: /etc/puppetlabs/code/environments/production/external-modules/chrony/templates/chrony.conf.epp, line: 102, column: 7) on node testserver01
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

however running directly against the production environment succeeds. Any ideas on what is going on ?

Attaching a log extract from the server.

puppetserver.log

[kenyon]

You probably have an older version of this module in your production environment, since ptpport was only added in the latest version, 5.0.0.

[barney-garrett]

You probably have an older version of this module in your production environment, since ptpport was only added in the latest version, 5.0.0.

nope ... we use git and g10k to deploy environments, development branches are merged into production and 5.0.0 was merged in March. We noticed that hosts that had been in development branches were not automatically reverting to Production when the development branch was removed.

Possibly silly question, I've just noticed that some of the development environments have not been rebased ... is it possible that is causing the issue ?

[kenyon]

Have a look at what version of the module is actually in the environment, such as with head /etc/puppetlabs/code/environments/production/external-modules/chrony/CHANGELOG.md

[barney-garrett]

head /etc/puppetlabs/code/environments/production/external-modules/chrony/CHANGELOG.md
# Changelog

All notable changes to this project will be documented in this file.
Each new release typically also includes the latest modulesync defaults.
These should not affect the functionality of the module.

## [v5.0.0](https://github.com/voxpupuli/puppet-chrony/tree/v5.0.0) (2025-11-27)

[Full Changelog](https://github.com/voxpupuli/puppet-chrony/compare/v4.0.0...v5.0.0)

init.pp and the chrony.config.epp both contain ptpport and ptpdomain.

  Optional[Integer[0]] $ptpport                                    = undef,
  Optional[Integer[0,255]] $ptpdomain                              = undef,

<% if $chrony::ptpport { -%>

# https://chrony-project.org/doc/latest/chrony.conf.html#ptpport
ptpport <%= $chrony::ptpport %>
<% } -%>
<% if $chrony::ptpdomain { -%>

[kenyon]

Maybe it is a cache issue, or a need to run puppet generate types 🤷