https://www.puppet.com/community logo
Join Slack
Powered by
# bolt
  • y
    what is shebang in the file? check 1st line there
  • y
    for me it’s 
    #! /opt/puppetlabs/puppet/bin/ruby
  • y
    so check if the file exists in your VM and it’s executable
  • y
    Copy code
    root@lima-limapark-ubuntu2404:~# /opt/puppetlabs/puppet/bin/ruby --version
ruby 3.2.5 (2024-07-26 revision 31d0f1a2e7) [aarch64-linux]
  • y
    also you can try to run the custom_facts.rb manually as root.. it should break but you’ll see how exactly at least
  • c
    Let me look into this deeper
  • j
    Hi team, I'm trying to speed up a bolt run and would like some assistance. I have a plan where I execute a run command and then want to run tasks based on the results, more details in thread
    y
    • 2
    • 9
  • c
    Whenever I run a `bolt plan run`command, it always gives me this error 
    Puppet is not installed on the target, please install it to enable 'apply'
    But when checking for the puppet version, it clearly returns a version which means Puppet is installed. I'm running this in an Ubuntu24 machine Any ideas whats causing this?
    b
    • 2
    • 29
  • d
    Ok, now I'm confused with the run_plan function. What is the definition of 
    $nodes
    vs 
    $targets
    ? If I have a plan with a 
    TargetSpec $targets
    i want to call with 
    run_plan
    . Do I use 
    run_plan('myplan', $targets, {'something'=>true})
    or do I use 
    run_plan('myplan', {'targets'=>$targets,'something'=>true})
    ? Is it just a shorthand or does it behave differently?
    v
    s
    +2
    • 5
    • 5
  • c
    are you in PE? My understanding is 
    bolt plan run <name>
  • c
    ```$ bolt help plan Name plan Usage bolt plan <action> [options] Description Convert, create, show, and run Bolt plans. Documentation Learn more about Bolt plans at https://pup.pt/bolt-plans. Actions convert Convert a YAML plan to a Bolt plan new Create a new plan in the current project run Run a plan on the specified targets show Show available plans and plan documentation Global options -h, --help Display help. --version Display the version. --log-level LEVEL Set the log level for the console. Available options are trace, debug, info, warn, error, fatal. --clear-cache Clear plugin, plan, and task caches before executing.
  • d
    Not in PE. I'm asking from writing an own plan which calls another plan, so I'm within writing plans context
  • j
    Need a little help... first time writing a bolt plan...Used Bolt to pull down cd4epe_job module which I then want to install on my CD4PE Job Worker Node... in .modules the directory cd4pe_jobs exists with the module in it. In my bolt plan, which I am writing in yaml.. Do I reference the class as puppetlabs/cd4pe_job or just cd4pe_jobs ?
  • y
    2nd
    thankyou 1
  • j
    Is it possible to run a PIM upgrade when you cannot ssh as root? With CD4PE I can ssh as a user and use the run-as item in the inventory.yaml to have it switch to root...Is this possible when using PIM?
  • n
    @natemccurdy has left the channel
  • a
    @austb has left the channel
  • t
    @Tino Müller has left the channel
  • m
    Can someone confirm if the latest Bolt release 5.0.0 has been uploaded to the repo yet? It does not seem to be included at the moment. I'm testing the noble ubuntu repo
    j
    • 2
    • 5
  • v
    does service task manage systemd timers or I need to use command instead?
    y
    k
    • 3
    • 4
  • t
    I'm running bolt in linux connecting to windows. Running a bolt plan I assume it's running in cmd when it connects, so it fails to make a tmpdir. Is this the reason? Do I need to change something so it uses powershell?
  • t
    Says the syntax of the command is incorrect. I'm connecting with ssh.
  • b
    I guess it assumes the target is Linux when you use ssh as transport protocol
  • b
    But since you don't share your code and error message, we can only guess
  • t
    Copy code
    groups:
  - name: test
    targets:
      - test.server
    config:
      transport: ssh
      ssh:
        tmpdir: 'd:\tmp'
        user: username
        private-key: ~/.ssh/id_rsa
  • t
    Copy code
    parameters:
  targets:
    type: TargetSpec
    description: A list of targets to run actions on
    default: localhost

# The steps key defines the actions the plan will take in order.
steps:
  - description: Update tomcat
    name: update_tomcat
    targets: $targets
    resources:
      - class: tomcat
        parameters:
          source_url: <https://dlcdn.apache.org/tomcat/tomcat-11/v11.0.11/bin/apache-tomcat-11.0.11-windows-x64.zip>
          catalina_home: d:\appservers
  • y
    Run bolt with 
    --debug --trace
  • y
    It should show more info about everything
  • t
    thanks
  • a
    Hi everyone👋, good afternoon from Italy! Just wanted to let you know I've submitted my first PR to fix the obsolete 'version' tag in the spec docker-compose file (related to issue #3392). While setting up the environment, I also found a build failure due to an expired GPG key and opened a new issue for that: #3396. Happy to be here and looking forward to contributing more!
    j
    • 2
    • 2