https://www.puppet.com/community logo
Join SlackCommunities
Powered by
# puppet-enterprise
  • n
    the puppet run fails when executing the GenerateZip command for bulk pluginsync because the command does not exist at the time of execution. 2019.8.11
  • c
    Yeah, it’s an ordering bug if I recall. A second run of the plan or regular agent run should succeed.
  • v
    I found no use for them
    Copy code
    pe_repo::enable_bulk_pluginsync: false
pe_repo::enable_windows_bulk_pluginsync: false
  • n
    Is that a code or doc fix?
  • v
    that's hiera
  • n
  • v
    I tend to add it to pe.conf as well
  • n
    bulk pluginsync is pretty useful when installing new agents.
  • v
    maybe if you have huge lib objects, I don't
  • n
    When every minute counts during provisioning.
  • n
    yea try installing the DSC module or other modules with lots of plugins and you go from minutes of pluginsync down to a second
  • b
    still brainstorming how a similar feature in FOSS puppetserver could look like
  • d
    Who can I grumble about `enterprise_tasks::run_puppet`` too? 🙂
  • d
    trying to get it to run with 
    additional_args
    and all it does is complain about the data type not being an array
  • s
    This message was deleted.
    d
    • 2
    • 2
  • v
    so add 
    ["--noop"]
    , for example
  • v
    as options
  • n
    Copy code
    warning: /var/cache/yum/x86_64/7Server/pc_repo/packages/puppet-agent-6.27.1-1.el7.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 9e61ef26: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet
 
 
The GPG keys listed for the "Puppet Labs puppet6 Repository" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.
 
 
Failing package is: puppet-agent-6.27.1-1.el7.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet
  • n
    I deleted the existing keys and run puppet, but it just synced down the same key files again. Not sure why there is a mismatch.
  • d
    thanks. After some banging my head on the desk, worked out the format for tags was two separate values in the array. Which is not what I was expecting it to be
  • s
    This message was deleted.
    n
    • 2
    • 2
  • d
    Normally some manual steps to import the new key, or remove the older key
  • d
    rpm does support multiple packaging keys for packagers to rotate gpg keys, but nobody ever seems to use it
  • s
    This message was deleted.
    n
    c
    +2
    • 5
    • 24
  • c
    The admin password set in 
    pe.conf
    , but may be omitted from the copy saved to 
    /etc/puppetlabs/enterprise/
    . In general, what you’re asking for may not exist any longer because it prevents hour(s) of time spent answering questions about plaintext passwords in files.
  • c
    The admin password set in 
    pe.conf
    may be omitted from the copy saved to 
    /etc/puppetlabs/enterprise/
    . In general, what you’re asking for may not exist any longer because it prevents hour(s) of time spent answering questions about plaintext passwords in files.
  • n
    there’s a typo in your runuser command
  • n
    why are queries for my node groups timing out. I only have 2000 nodes total and it has trouble when even 20 nodes are in a group.
  • s
    This message was deleted.
    n
    n
    +2
    • 5
    • 25
  • n
    What query is pe console doing to retrieve node lists for a group. I want to execute the sql or whatever to see if I can pinpoint my issue. I want to blame the hardware. “Error retrieving node list: There was an error connecting to PuppetDB: 60,000 milliseconds timeout on connection http-outgoing-6183 [ACTIVE]”
1...91011...73Latest