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

non existing env causes undefined method `environment_data_provider' for nil:NilClass error

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.9.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Puppet Developer Experience
    • Story Points:
      1
    • Sprint:
      PDE 2017-01-25
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      A node group configured to use an environment which didn't exist would sometimes fail with error "NoMethodError: undefined method `environment_data_provider' for nil:NilClass". The bug was caused by code in the experimental lookup API (Hiera version 4) and was fixed as part of the rewrite to version 5.
      Show
      A node group configured to use an environment which didn't exist would sometimes fail with error "NoMethodError: undefined method `environment_data_provider' for nil:NilClass". The bug was caused by code in the experimental lookup API (Hiera version 4) and was fixed as part of the rewrite to version 5.
    • QA Risk Assessment:
      No Action

      Description

      In the edge case in which a node group is configured to use an environment which doesn't exist, the compiler sometimes blows up spectacularly with a stack traces and an error message like the following:

      Puppet::Parser::Compiler failed with error NoMethodError: undefined method `environment_data_provider' for nil:NilClass
      

      This can easily occur if the node group is configured to use environments deployed via Code Manager, and then the branch representing the environment is deleted & deployed.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ben.ford Ben Ford
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support