https://www.puppet.com/community logo
Join Slack
Powered by
# puppet-enterprise
  • b
    that server has lockless deploys enabled, so the correct code dir is 
    /etc/puppetlabs/puppetserver/code
    , not 
    /etc/puppetlabs/code
    anymore
  • m
    ah.. yes this could be a bit of a gotcah
  • b
    but the code-staging dir is still the same
  • b
    rm -rf the env in code-staging
  • b
    yep, that fixed it
  • s
    This message was deleted.
    t
    c
    • 3
    • 22
  • t
    Copy code
    root@primary:/etc/puppetlabs/puppet# puppet infrastructure provision compiler <compiler.fqdn> --dns-alt-names <lb fqdn>
Provisioning compiler on <compiler fqdn>. This may take several minutes.

Running enterprise_tasks::provision_compiler plan.

Starting: plan enterprise_tasks::provision_compiler
Starting: task enterprise_tasks::test_connect on <primary>
Finished: task enterprise_tasks::test_connect with 0 failures in 0.06 sec
Verify_node: <primary> verified to have the primary role.
Starting: task enterprise_tasks::check_pp_auth_role_rule on <primary fqdn>
Finished: task enterprise_tasks::check_pp_auth_role_rule with 0 failures in 1.28 sec
Starting: plan enterprise_tasks::is_subject_alt_names_allowed
Starting: task enterprise_tasks::get_conf_values on <primary fqdn>
Finished: task enterprise_tasks::get_conf_values with 0 failures in 0.35 sec
Finished: plan enterprise_tasks::is_subject_alt_names_allowed in 0.59 sec
Starting: command /opt/puppetlabs/bin/puppet config print certname --section agent on <primary fqdn>
Finished: command /opt/puppetlabs/bin/puppet config print certname --section agent with 0 failures in 1.19 sec
Starting: task enterprise_tasks::test_connect on <compiler fqdn>,<primary fqdn>
Finished: task enterprise_tasks::test_connect with 0 failures in 0.05 sec
Starting: task enterprise_tasks::disable_agent on <primary fqdn>
Finished: task enterprise_tasks::disable_agent with 1 failures in 1 min, 0 sec
Errors in task enterprise_tasks::disable_agent:
 <primary fqdn>:
  Message:
  Kind:
  Details:
   nil
Starting: task enterprise_tasks::enable_agent on <primary fqdn>
Finished: task enterprise_tasks::enable_agent with 1 failures in 0
Error: Request to https://<primary fqdn>:8143/orchestrator/v1/plan_jobs/5 failed after 0.001 seconds: Failed to open TCP connection to <primary fqdn>:8143 (Connection refused - connect(2) for "<primary fqdn>" port 8143)
Wrapped exception:
Failed to open TCP connection to <primary fqdn>:8143 (Connection refused - connect(2) for "<primary fqdn>" port 8143)
Error: Try 'puppet infrastructure help provision' for usage
  • t
    SOLVED!!! We had to set the 
    file_sync_enabled
    parameter from “`automatic"` to 
    true
    on the PE Compiler node group
  • t
    SOLVED!!! We had to set the 
    file_sync_enabled
    parameter from 
    "automatic"
    to 
    true
    on the PE Compiler node group
  • t
    PEBCAK! We added the data to a node hierarchy. Only primary received the information. We missed the data for the compiler.
  • s
    This message was deleted.
    m
    y
    s
    • 4
    • 4
  • s
    This message was deleted.
    d
    a
    +2
    • 5
    • 11
  • s
    This message was deleted.
    r
    d
    • 3
    • 14
  • s
    This message was deleted.
    m
    b
    +2
    • 5
    • 23
  • s
    This message was deleted.
    r
    d
    • 3
    • 3
  • r
    hi, we are trying to run cd4p behind a f5 lb and only get connection refused for the 443 cd4pe webfrontend. ingress/k8s/deployments look fine. when we connect to the hostname of cd4pe we get the interface, but if we configure it to the lb-name, we only get connection refused. are there any hints, how to run cd4pe with F5?
  • b
    Another question, I noticed that I've ~8GB of data in 
    /opt/puppetlabs/server/apps/puppetserver/tmp
    . Now this sounds like a temporary directory to me, but it has ~6k files, some 2 years old: https://gist.github.com/bastelfreak/5b44966aca492338b53d2dce0305e774 . Does someone now if this is expected/ can be deleted? (Running PE 2019.8.12 and 2021.7.1). Data won't be deleted during a pe-puppetserver restart
  • b
    Another question, I noticed that I've ~8GB of data in 
    /opt/puppetlabs/server/apps/puppetserver/tmp
    . Now this sounds like a temporary directory to me, but it has ~6k files, some 2 years old: https://gist.github.com/bastelfreak/5b44966aca492338b53d2dce0305e774 . Does someone now if this is expected/ can be deleted? (Running PE 2019.8.12 and 2021.7.1)
  • b
    Another question, I noticed that I've ~8GB of data in 
    /opt/puppetlabs/server/apps/puppetserver/tmp
    . Now this sounds like a temporary directory to me, but it has ~6k files, some 2 years old: https://gist.github.com/bastelfreak/5b44966aca492338b53d2dce0305e774 . Does someone now if this is expected/ can be deleted? (Running PE 2019.8.12 and 2021.7.1). Data won't be deleted during a pe-puppetserver restart
  • l
    @lindsley has left the channel
  • n
    It’ll be in the next release 🙂
  • n
    Just removing from config scope (or all, which includes config), because you might get a very long initial deploy after restore if you have a large code base.
  • n
    I guess it’s still going to get excluded in the 
    all
    case. It just won’t be excluded in 
    --scope code
     nm, it’s not in the included path for code
  • r
    is there a plan, time, date, range when PE will support Ubuntu 22.04 / RHEL 9 as a Primary/Replica/Compiler (puppetserver)? the documentation says nothing about this: https://puppet.com/docs/pe/2021.7/supported_operating_systems.html#supported_operating_systems
  • g
    Hi @Robert Waffen - there are some final decisions being made this week about 2023 roadmap - so we should have some more info towards the end of this week if not early next on that - stay tuned. Also - please raise this with your Puppet Account Manager / rep to make sure they are feeding into the product team your request. Many thanks, Gareth…
  • g
    Hi @Robert Waffen - there are some final decisions being made this week about 2023 roadmap - so we should have some more info towards the end of this week if not early next on that - stay tuned. Also - please raise this with your Puppet Account Manager / rep to make sure they are feeding into the product team your request. Many thanks, Gareth…
  • b
    a few questions: • Wouldn't it make sense to ask Puppet Solutions Providers for roadmap decisions? • Why does it need to be raised through an account manager and not something else, like the ENTERPRISE jira board?
  • g
    Puppet has the Puppet Product Board to raise new features/make requests - the idea there is to focus all/any requests in one channel for the Product folks. However if you are a cusotmer you can also raise any requests via your account manager also to feed into the product cycle.
  • g
    In my mind this should be similar for Solutions Partners either use the Product board or your Puppet Contact point…
  • b
    I raised a few requests in the product board and never got feedback, so that made quite a poor user experience
1...303132...73Latest