Orchestration services known issues

This version is out of date. For current versions, see Puppet Enterprise support lifecycle.

This page lists known issues for orchestration services in Puppet Enterprise.

Orchestrator jobs on Windows agents can’t be terminated with CTRL+C

If you need to stop an orchestration job running on a Windows agent, you can use the /command/stop API endpoint.

Agents in Puppet job runs may request incorrect environment

When you use the Puppet orchestrator puppet job command with the environment flag, Puppet agent runs participating in the job should request the specified environment. A known issue exists where these agent runs may request a catalog for a different environment than the one specified in the job.

To workaround this issue, we recommend that you use the node classifier in the PE console to add agents to the environment that will be participating in Orchestration jobs. Alternatively, you could assign the agent’s environment in its configuration file.

See an issue? Please file a JIRA ticket in our [DOCUMENTATION] project
Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.