Puppet Enterprise 2018.1

These are the known issues for the console and console services in this release.

NEW: Dynamic node matching using either start- or end-of-line regex erroneously shows no matches


When using a start-of-line anchor (^) or an end-of-line anchor ($) to dynamically match nodes in the console, no matches are found, even if matches exist. For example, if you have a node named jupiter, using a regex match (~) for iter shows 1 match, but using a regex match iter$ shows no matches.

This issue affects your ability to preview the matching of classification rules in the console, but it does not affect classification, and classes are still applied.

As a workaround, you can add an extra double quotation mark (") to the regex when previewing classification in the console. For example, to match the hostname jupiter, use the regex ^"jupiter.
Important: Remove the extra quotation mark before saving the rule, because it won't match in the classifier.

Deactivated nodes shown in Packages page summary counts

If all the nodes on which a certain package is installed are deactivated, but the nodes' specified node-purge-ttl period has not yet elapsed, instances of the package still appear in summary counts on the Packages page. To correct this issue, adjust the node-purge-ttl setting and run garbage collection.

Reports page summary counts might be inaccurate on first usage

Report count caching is used to improve console performance. In some cases, caching might cause summary counts of available reports to be displayed inaccurately the first time the page is accessed after a fresh install.

Updated modes are shown without leading zero in events

When the mode attribute for a file resource is updated, and numeric notation is used, leading zeros are omitted in the New Value field on the Events page. For example, 0660 is shown as 660 and 0000 is shown as 0.

Performance issues with the unpin-from-all endpoint

As number of groups increases, response time can increase significantly with the unpin-from-all endpoint.

Agent time skew results in incorrect error message

If an 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".

Back to top