Either the task doesn’t appear in the console in the Task field, or when you run puppet task
in the command line, you get a message that the task isn’t found.
Version and installation information
PE version: All supported
Solution
When a task is missing or won’t load, make sure that you:
- Install the task you want to use.
- Have access to the node or list of nodes you want to target. If you’re using a node group, make sure there’s at least one matching node.
- Have Permission to run:
- The task
- PQL query
- Check there are no errors after you deploy code.
- Check for Bolt projects in the root of your code directory and remove them.
Note: When you save a task with large files to the control repository, it might take a couple of minutes for your task to appear in the console.
Invalid task/script name
Each task or plan name segment must begin with a lowercase letter and:
- Can include digits.
- Can include underscores.
- Namespace segments must match the following regular expression
/A[a-z][0-9]*\Z
- The file extension must not use the reserved extensions .md or .json.
See Naming tasks in our documentation. This section also includes information on how to name single platform tasks and cross-platform tasks.
Missing or unformatted metadata
Make sure your JSON file is formatted correctly and isn’t missing metadata.
Note: To help ensure syntax is valid when writing Puppet code, tasks, and plans, use an IDE, such as Visual Studio Code, with the Puppet extension.
Authentication issues
- Make sure the task is installed in the correct environment.
- Before you run Puppet orchestrator, make sure you generate a token using
puppet-access
.
How can we improve this article?
0 comments
Please sign in to leave a comment.
Related articles