Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCUMENT-1185

More info about a node can belong to only one Puppet-Environment Group

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Component/s: None
    • Labels:
    • Template:
    • Story Points:
      5
    • Sprint:
      2021.2.02-2.16, 2021.3.30-4.13, 2021.4.13-4.27
    • QA Risk Assessment:
      Needs Assessment

      Description

      Hi,

      PE Customers, esp new users, need to understand this section really well:

      https://puppet.com/docs/pe/2019.8/grouping_and_classifying_nodes.html#creating_node_groups

      The policy around node groups that any node can belong to is the following:


      "A node can be part of many node groups, a mix of environment and classification node groups.

      However, among those node groups, there can be only one (puppet-)environment group, which declares the (puppet-)environment a node checks into.

      A "Puppet-Environment Group" is mapped directly to a git branch of the Control repo (i.e: a preprod environment group matches the preprod branch of the control repo). In the case of a node being assigned to more than 1 environment group, would result in a "Classfication Conflict" Error message during the Puppet agent run.

      You can find KB articles that discuss this issue here: "https://support.puppet.com/hc/en-us/search?utf8=%E2%9C%93&query=classification+conflict"


       

      Thanks!

        Attachments

        1. env_group.png
          15 kB
          Rajesh Radhakrishnan
        2. one_env_group.png
          47 kB
          Rajesh Radhakrishnan

          Activity

            People

            Assignee:
            logan.mantyla Logan Mantyla
            Reporter:
            rajesh.radhakrishnan Rajesh Radhakrishnan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support