This page lists known issues for the PE console and console services in Puppet Enterprise.
You can file bugs for issues you identify in our issue tracker.
mode attribute for a
file resource is updated, and numeric notation is used, leading zeros are dropped in the New Value field on the Events page. For example,
0660 is shown as “660” and
0000 is shown as “0.”
If you view the node graph for a node with a newly compiled catalog during a Puppet run, the graph will have a status of “unknown” and will display grey status indicators. During a Puppet run, the catalog is submitted early in the run, but the report is generated at the end. Mid-run, the node’s structure can be graphed, but its status is unknown. Once the Puppet run has completed, reopen the node graph to see the node’s current status.
In certain situations, the enforcement of non-idempotent resource types can cause inaccurate reports of corrective change. Non-idempotent resources such as custom resource types or exec resources that do not adhere to idempotency best practices might cause this behavior. The first time Puppet applies an exec resource it will be reported as an intentional change. All subsequent changes will be reported as corrective changes, even if the Puppet code for the exec resource was intentionally modified.
As number of groups increases, response time can increase significantly with the
If a PE agent attempts to check in with the master but the agent has significant time skew, an incorrect error message is returned. This message masks the real cause of the problem, which is the time skew. The error message says:
400 Error: "Attempt to assign to a reserved variable name: 'trusted' on node".