Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-5522

Puppet node does not keep attributes consistent with parameters

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 3.8.5, PUP 4.3.2
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      Language 2015-12-02, Language 2015-12-16
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Some Puppet related applications (and advanced use cases using puppet from Ruby) could end up with a Node object that used one environment but reported it was in another. The observable wrong behavior in those cases would be that the node could end up with the wrong set of parameters. This problem has not been observed for regular catalog compilation.
      Show
      Some Puppet related applications (and advanced use cases using puppet from Ruby) could end up with a Node object that used one environment but reported it was in another. The observable wrong behavior in those cases would be that the node could end up with the wrong set of parameters. This problem has not been observed for regular catalog compilation.

      Description

      The Puppet::Node class has two attributes, environment_name and environment. It also has a parameter named 'environment'. These are not kept in sync which causes problems for the catalog_preview application. See PRE-81. I think it's better to fix this in the puppet code than adding a workaround in the catalog preview program.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  thomas.hallgren Thomas Hallgren
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support