https://www.puppet.com/community logo
Join Slack
Powered by
# bolt
  • y
    could you check if any other task runs? e.g. 
    bolt task run package -t <VM> name=bash action=status
  • c
    Here's the output 
    {
    "status": "installed",
    "version": "5.2.21-2ubuntu4"
    }
  • y
    so task executor is good
  • y
    @Christian Michael Tan try 
    bolt apply
    with 
    --log-level=trace
    , it’ll dump more debug info
  • c
    Sure let me try. The previous logs I sent was run using log-level debug
  • y
    it seems you have tmpdir settings changed to 
    /home/<user>
    , because all files I see are uploaded to 
    /tmp
    subdir
  • c
    Yes correct, will the setting impact the bolt apply run? (other than the dependency files wont get deleted after VM reboot)
  • y
    ideally no, just found that from the output
  • c
    Okay it turns out custom_facts.rb is getting successfully uploaded `Command 
    mkdir -m 700 /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f
    returned successfully` 
    Uploading /opt/puppetlabs/bolt/lib/ruby/gems/3.2.0/gems/bolt-4.0.0/libexec/custom_facts.rb to /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f/custom_facts.rb
    `Executing `chmod u+x /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f/custom_facts.rb`` `Command 
    chmod u+x /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f/custom_facts.rb
    returned successfully` `Executing `id -g root`` `Command 
    id -g root
    returned successfully`
  • c
    I am having this odd log: `Executing `sudo -S -H -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\ sh -c cd\;\ chown\ -R\ root:0\ /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f`` `Command 
    sudo -S -H -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  sh -c cd\;\ chown\ -R\ root:0\ /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f
    returned successfully` `Executing `sudo -S -H -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\ sh -c echo\ d7e93e12-01e1-4aa1-ae73-b0838511c745\ 1\>\&2\;\ cd\;\ /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f/custom_facts.rb`` 
    Command sudo -S -H -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  sh -c echo\ d7e93e12-01e1-4aa1-ae73-b0838511c745\ 1\>\&2\;\ cd\;\ /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f/custom_facts.rb failed with exit code 127
    `Executing `sudo -S -H -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\ sh -c cd\;\ rm\ -rf\ /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f`` `Command 
    sudo -S -H -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  sh -c cd\;\ rm\ -rf\ /home/pgadmin/ce65b898-868b-46d6-9bed-1c1fa95bb78f
    returned successfully` 
    Closed session
  • y
    Copy code
    Executing `sudo -S -H -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  sh -c echo\ c4c82093-aa24-4f76-b073-b62d06de2360\ 1\>\&2\;\ cd\;\ /tmp/8536a2b4-f062-4c1a-a51e-b5585b378a0f/apply_catalog.rb`
Command `sudo -S -H -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  sh -c echo\ c4c82093-aa24-4f76-b073-b62d06de2360\ 1\>\&2\;\ cd\;\ /tmp/8536a2b4-f062-4c1a-a51e-b5585b378a0f/apply_catalog.rb` returned successfully
  • y
    this how it looks on my side
  • y
    there was a way to prevent cleanup.. let me find it
  • y
    Copy code
    config:
  ssh:
    cleanup: false
  • y
  • c
    Its saying that its not able to find the custom_facts.rb file 
    Skipping cleanup of tmpdir /home/pgadmin/2c409c8d-74ac-4997-a5ab-e30e7752f44b [ID: skip_cleanup]
    Closed session
    {"target":"10.121.140.11","action":"task","object":"apply_helpers::custom_facts","status":"failure","value":{"_output":"","_error":{"kind":"puppetlabs.tasks/task-error","issue_code":"TASK_ERROR","msg":"The task failed with exit code 127 and no stdout, but stderr contained:\nsh: 1: /home/pgadmin/2c409c8d-74ac-4997-a5ab-e30e7752f44b/custom_facts.rb: not found\n","details":{"exit_code":127}}}}
    But it definitely exists in the VM
  • 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