Node run statuses

This node’s last Puppet run failed or Puppet encountered an error that prevented it from making changes.

The error is usually tied to a particular resource (such as a file) managed by Puppet on the node. The node as a whole might still be functioning normally. Alternatively, the problem might be caused by a situation on the primary server that is preventing the node's agent from verifying whether the node is compliant.

With corrective changes

During the last Puppet run, Puppet found inconsistencies between the last applied catalog and this node’s configuration, and Puppet corrected those inconsistencies to match the catalog.

Corrective change reporting is available only on agent nodes running Puppet Enterprise (PE) 2016.4 and later. Agents running earlier versions report all change events as With intentional changes.

With intentional changes

During the last Puppet run, catalog changes were successfully applied to the node.

Unchanged

This node's last Puppet run was successful, and the node was fully compliant. No changes were necessary.

With failures

This node’s last no-op Puppet run failed or Puppet encountered an error that prevented it from simulating changes.

Would have corrective changes

During the last no-op Puppet run, Puppet found inconsistencies between the last applied catalog and this node’s configuration, and, in a true run,Puppet would correct those inconsistencies to match the catalog.

Would have intentional changes

If the last no-op Puppet run had been a true run, catalog changes would have been applied to the node.

Would be unchanged

This node’s last no-op Puppet run was successful, and the node was fully compliant. In a true run, no changes would have been necessary.

Unresponsive

The node hasn't reported to the primary server recently. Something might be wrong.

The run status table shows the timestamp for the node's last known Puppet run and whether the node's last known run was in no-op mode. Correct the problem to resume Puppet runs on the node.

The default cutoff time for considering a node unresponsive is one hour, but you can change this with the puppet_enterprise::console_services::no_longer_reporting_cutoff parameter. Go to Configure the PE console and console-services for more information.

Have no reports

Although Puppet Server is aware the node exists, the node has never submitted a Puppet report because the node is a new node, the node has never come online, or the node's copy of Puppet is not configured correctly.

Expired or deactivated nodes are shown on the Status page for seven days. To extend the amount of time that you can view or search these nodes, change the node-ttl setting in PuppetDB. Changing this setting impacts resources and exported resources.

During the last Puppet run, the intended catalog for this node failed and Puppet substituted a cached catalog, according to your configuration settings.

This typically occurs if there are compilation errors in your Puppet code. Check the Puppet run log for details.

This category is shown only if one or more agents failed to retrieve a valid catalog from Puppet Server.

During the last no-op Puppet run, one or more resources were enforced, according to your use of the noop => false metaparameter setting.

This category is shown only if enforced resources are present on at least one node.