Legacy: Modify a Puppet node

Change management prevents Puppet users from directly editing the Configuration automation or Node definition fields on the CI form.

Before you begin

Role required: puppet_admin

About this task

A Puppet administrator can directly configure Puppet settings for a specific node from the CI form. To view a list of CIs that use Puppet configuration automation and are assigned to the logged-in user, navigate to Configuration Automation > Managed Nodes. By default, a Puppet user cannot directly modify the Puppet fields on the CI form, and must request changes through a controlled change process.

Note: Updates to a CI reset the Node group assignment state to Ready. The Ready state ensures that assignment rules are applied and that the CIs are re-assigned based on the new values. For example, updating fqdn or IP address might reassign a CI to a different node group.

Procedure

  1. Navigate to Configuration Automation > Managed Nodes or Configuration > Servers > Linux.
  2. Open the node to update.
  3. Edit the fields under the Configuration Automation related list.
    Table 1. CI form
    Field Description
    Fully qualified domain name The fully qualified domain name that Puppet uses to access this CI.
    Provider The configuration automation provider managing this CI.
    Management Server The server managing this CI.
    Node group assignment state The state of automatic assignment of this CI to a node group, as described in the following table.
    State Description
    Ready Default state for newly discovered CIs. Assignment rules are applied only to CIs in the Ready state.
    In Progress CI is currently experiencing a configuration change.
    Assigned CI is part of one or more node groups.
    Processed Assignment rules have been applied to the CI. There may or may not be a match.
    Excluded Configuration admin role can exclude a CI from being processed by the assignment rules.
  4. Click Update.