https://www.puppet.com/community logo
Join Slack
Powered by
# puppet-enterprise
  • v
    also, seems some dependencies are missing
    Copy code
    2026-07-24T16:50:14.555+00:00 - [Error]: Could not find a suitable provider for cron
  • v
    I guess original question stand - is it really supported?
  • b
    I am still dreaming about a future with systemd timers and no crons
    ☝🏼 1
    💯 1
    ➕ 1
  • s
    I recall something else about Amazon 2023. No 
    syslog
    by default, maybe?
  • v
    nope, only journald
  • b
    This is the way
  • j
    @vchepkov: Amazon 2023 is supposed to be supported as a platform, this sounds like a bug with PEADM.
  • t
    On PE 2025.11.0 when managing EC encryption using a Puppet custom function the pe-puppetserver throws an exception. Same error message as in older OpenVox server packages: github.com/OpenVoxProject/openvox-server/issues/322. Solution is to upgrade jruby-openssl
    s
    m
    • 3
    • 4
  • t
    Why are there environements with empty name in puppetdb? Customer queries puppetdb for env using: curl localhost/pdb/query/v4/environments | python3 -m json.tool
  • t
    Result:
  • t
    Copy code
    [
    {
        "name": "production"
    },
    {
        "name": ""
    },
    {
  • t
    And: how to get rid of the env with empty name? We also see entries in postgresql referencing the empty env id
  • t
    /opt/puppetlabs/server/bin/psql -d pe-puppetdb -c ‘select * from environments;’ id | environment -----+------------------------------------------------------------------- 1 | production 258 | 259 |
  • t
    /opt/puppetlabs/server/bin/psql -d pe-puppetdb -c ‘select count(*) from reports where environment_id = 258;’ count ------- 5 (1 row)
  • t
    select id, certname, puppet_version, producer_timestamp from reports where environment_id = 258;
  • t
    shows us that this occurred during PE 2025.11 update on the replica.
  • t
    Correction: the reports have been stored during the upgrade of the primary, but with the old puppet agent version on the replica.
  • j
    Need some help.. Have Vulns for Postgres 4.22 with remediation to 4.23, But PE 2025.10 is at 4.22 with 2025.11 jumping to Postgres 17. Same Vuln sez it needs to be at least 17.10. Can I get some help / validation that Postgres goes to 17.10 in 2025.11 before I make this jump?
    t
    j
    • 3
    • 7
  • c
    Along with the theme of vulnerabilities scans I see our scanner is flagging nginx/1.28.2 as EOL. Newer version coming soon in PE?
    t
    • 2
    • 1
  • v
    A heads up - PE2025.11.2 release breaks eyaml. From what I can tell BouncyCastle 1.85 is to blame
    s
    • 2
    • 3
  • v
    yep. here is the story PE 2025.11.2 ships /opt/puppetlabs/share/java/bcprov-jdk18on-1.85.jar; 2025.11.0 shipped 1.84. BouncyCastle 1.85 rejects X.509 certificates whose issuer DN is empty. Certificates produced by "eyaml createkeys" have an empty subject AND an empty issuer DN, so they can no longer be parsed inside puppetserver.
  • s
    yep, repro'd here
  • j
    Ugh So don't go there or is there an easy workaround?
    s
    • 2
    • 3
  • v
    I hacked pkcs7.rb
  • v
    But I won't go prod with that 🙂
  • b
    patches welcome 🙂
    s
    s
    v
    • 4
    • 35
  • j
    Thanks Everyone for sharing...
  • e
    it also fails for us here:
    Copy code
    2026-08-27T21:01:52.439+00:00 [ERROR]: Your pe.conf file at /opt/puppetlabs/server/data/staging/pe_repo-puppet-agent-8.20.0/puppet-enterprise-2025.11.2-el-9-x86_64/conf.d/custom-pe.conf contains errors.
2026-08-27T21:01:52.446+00:00 [ERROR]: Check your pe.conf file for errors and try re-running the installer.
  • e
    unfortunately this was also supposed to fix the compilers-fail-to-check-in-after-MoM-restarts thing so looks like we're stuck 😢
  • e
    ah. so earlier in the log, I see this:
    Copy code
    ## We're checking if /opt/puppetlabs/server/data/staging/pe_repo-puppet-agent-8.20.0/puppet-enterprise-2025.11.2-el-9-x86_64/conf.d/custom-pe.conf contains valid HOCON syntax...

2026-08-27T21:09:31.367+00:00 Running command: /opt/puppetlabs/installer/bin/validate_pe_conf.rb /opt/puppetlabs/server/data/staging/pe_repo-puppet-agent-8.20.0/puppet-enterprise-2025.11.2-el-9-x86_64/conf.d/custom-pe.conf
./puppet-enterprise-installer: line 665: /opt/puppetlabs/installer/bin/validate_pe_conf.rb: No such file or directory
2026-08-27T21:09:31.382+00:00 [ERROR]: !! Validation failure. !!
Rolling puppet-agent back to 8.20.0.
Rolling pe-installer back to PE 2025.11.0.
Rolling pe-modules back to PE 2025.11.0.
    something missing from the installer build?
    s
    c
    • 3
    • 5
1...6970717273Latest