https://www.puppet.com/community logo
Join SlackCommunities
Powered by
# puppet-enterprise
  • n
    ahh: /opt/puppetlabs/installer/share/Boltdir/site-modules/enterprise_tasks
  • v
    or start from here 🙂
  • v
    Copy code
    /opt/puppetlabs/server/data/environments/enterprise/modules/pe_manager/lib/puppet/face/infrastructure/enable.rb
  • n
    I have been looking for that. Thamks
  • s
    This message was deleted.
    n
    s
    g
    • 4
    • 5
  • s
    This message was deleted.
    b
    • 2
    • 2
  • s
    Check of relevant directories:
    Copy code
    ll /etc/puppetlabs/puppetserver/code
lrwxrwxrwx. 1 pe-puppet pe-puppet 20 Jun 27 11:22 /etc/puppetlabs/puppetserver/code -> /etc/puppetlabs/code
ll /etc/puppetlabs/code

drwxr-xr-x. 3 pe-puppet pe-puppet 24 Jun 27 14:56 environments
ll /etc/puppetlabs/code/environments/

drwxr-x---. 2 pe-puppet pe-puppet 6 Jun 27 14:53 production
ll /etc/puppetlabs/code/environments/production/

ll /opt/puppetlabs/server/data/puppetserver/filesync/client/versioned-dirs/

drwxr-x---. 2 pe-puppet pe-puppet  6 Jun 27 15:12 puppet-code
ll /opt/puppetlabs/server/data/puppetserver/filesync/client/versioned-dirs/puppet-code
    Solution: Clear /opt/puppetlabs/server/data/puppetserver/filesync/client/worktrees/puppet-code/ 
    rm -rf /opt/puppetlabs/server/data/puppetserver/filesync/client/worktrees/puppet-code/*
  • s
    This message was deleted.
    b
    n
    +3
    • 6
    • 6
  • s
    This message was deleted.
  • b
    [@simonhoenscheid’s message] I wanted to share something with the community, I had trouble with this week: We have a single Puppet Enterprise Primary Server Version 2021.6.0 used for testing purposes. Decided to test lockless deployments. The server had lockless deployments activated before. 1. set 
    puppet_enterprise::profile::master::versioned_deploys: true
    2. run 
    puppet agent -t
    3. run 
    puppet agent -t
    Run Fails, server unavailable 4. run 
    puppet code deploy --all --wait
    2022/06/27 16:16:23 ERROR - Post "https://<redacted>:8170/code-manager/v1/deploys": dial tcp <redacted>:8170: connect: connection refused
    Checking the 
    puppetserver.log
    : {...SNIP...] 
    2022-06-27T13:52:39.302+02:00 INFO  [e43c018e-0d75-4396-9e43-28338b1ec0f4_Worker-5] [p.e.s.a.analytics-core] Not checking for updates - opt out file /etc/puppetlabs/puppetserver/opt-out exists.
    2022-06-27T13:52:39.916+02:00 INFO  [clojure-agent-send-off-pool-2] [p.e.s.f.versioned-sync] Syncing live directory at /etc/puppetlabs/puppetserver/code for repository puppet-code
    2022-06-27T13:52:42.443+02:00 ERROR [clojure-agent-send-off-pool-2] [p.e.s.f.file-sync-client-core] Fatal error during file sync, requesting shutdown.
    org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files:
    [VERY LONG FILE LIST]
    [4:44 AM] Check of relevant directories:
    Copy code
    ll /etc/puppetlabs/puppetserver/code
lrwxrwxrwx. 1 pe-puppet pe-puppet 20 Jun 27 11:22 /etc/puppetlabs/puppetserver/code -> /etc/puppetlabs/code
ll /etc/puppetlabs/code

drwxr-xr-x. 3 pe-puppet pe-puppet 24 Jun 27 14:56 environments
ll /etc/puppetlabs/code/environments/

drwxr-x---. 2 pe-puppet pe-puppet 6 Jun 27 14:53 production
ll /etc/puppetlabs/code/environments/production/

ll /opt/puppetlabs/server/data/puppetserver/filesync/client/versioned-dirs/

drwxr-x---. 2 pe-puppet pe-puppet  6 Jun 27 15:12 puppet-code
ll /opt/puppetlabs/server/data/puppetserver/filesync/client/versioned-dirs/puppet-code
    Solution: Clear /opt/puppetlabs/server/data/puppetserver/filesync/client/worktrees/puppet-code/ 
    rm -rf /opt/puppetlabs/server/data/puppetserver/filesync/client/worktrees/puppet-code/*
  • s
    This message was deleted.
    s
    • 2
    • 2
  • d
    Or is that feature in a newer release?
  • d
    Also, is there any way to specify Puppet options, like 
    --ignoreschedules
    to the 
    group_patching
    plan? 🙂
  • s
    This message was deleted.
    s
    i
    c
    • 4
    • 8
  • g
    8/ bbxz-
  • s
    This message was deleted.
    g
    • 2
    • 1
  • t
    We recently, upgraded our puppet enterprise from 
    2019.8.10
    to 
    2019.8.11
    . After the upgrade, the agent version showing when I run 
    /opt/puppetlabs/bin/puppet --version
    shows version 
    6.27.0
    but per this documentation 
    <https://puppet.com/docs/pe/2019.8/what_gets_installed_and_where.html#what_gets_installed_and_where>
    the version is supposed to be 
    6.27.1
    . On an agent machine, I see that the package installed is 
    6.27.1-1focal
    . When I set the 
    package_version
    to 
    6.27.0
    a puppet run fails with the error below but when I set the version to 
    6.27.1
    , puppet is happy. I'm I missing something as to why the puppet agent is showing as having version 
    6.27.0
    when the 
    6.27.1
    package is installed?
    Copy code
    Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppet-agent=6.27.0-1focal' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
W: --force-yes is deprecated, use one of the options starting with --allow instead.
E: Version '6.27.0-1focal' for 'puppet-agent' was not found
Error: /Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure: change from '6.27.1-1focal' to '6.27.0-1focal' failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppet-agent=6.27.0-1focal' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
W: --force-yes is deprecated, use one of the options starting with --allow instead.
E: Version '6.27.0-1focal' for 'puppet-agent' was not found
  • v
    That was discussed, in general, one should not expect puppet agent package version match puppet component version. That happened several times in the past
  • v
    puppetlabs/puppet_agent module was fixed to handle it properly, maybe you need an update
  • t
    @vchepkov thank you! When i upgraded the 
    puppetlabs/puppet_agent
    module, at the time, the latest version was 
    4.11.0
    . I will update now to see if that fixes it.
  • v
    yep. that's where the fix was
  • v
  • v
    I set package to 6.27.1, since that the version you want
  • v
    or use 
    auto
  • t
    I just updated the agent module but the package version and component version still don't match so I guess I will take it that those two are not expected to match.
  • s
    This message was deleted.
    n
    n
    +2
    • 5
    • 12
  • t
    Now, I know. I didn't know I had to do that.
  • s
    This message was deleted.
    m
    b
    • 3
    • 2
  • b
    hey puppet people, I've PR at https://github.com/puppetlabs/puppetlabs-satellite_pe_tools/pull/180 . That's a required change for me to use it on PE 2021. Could someone take a look at it?
  • c
    Can someone tell me why when you run something like pdk with ruby 2.5 it pulls in activesupport 7 which requires ruby 2.7? Shouldn't the dependencies properly update the Gemfile.lock to latest activesupport 6 which still supported ruby 2.5.0?
1...141516...73Latest