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

"Attempt to redefine entity" caused by upper/lower case name confusion in Loader

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • PUP 4.10.1
    • PUP 4.10.3, PUP 5.0.0
    • None
    • None
    • Hide

      That it is impossible to create a Puppet::Pops::Loader::TypedName that contains an uppercase letter. This criteria can only be tested from Ruby code.

      Show
      That it is impossible to create a Puppet::Pops::Loader::TypedName that contains an uppercase letter. This criteria can only be tested from Ruby code.
    • Agent
    • 2
    • Agent 2017-06-14, Agent 2017-06-28
    • Customer Feedback
    • Bug Fix
    • Hide
      Intermittently Puppet would report errors on the form "Attempt to redefine entity" when "puppet generate types" was being used. This was caused by internal puppet logic not being consistent about names in upper/lower case. This is now fixed.
      Show
      Intermittently Puppet would report errors on the form "Attempt to redefine entity" when "puppet generate types" was being used. This was caused by internal puppet logic not being consistent about names in upper/lower case. This is now fixed.
    • No Action
    • change includes spec tests

    Description

      A load of a resource type will sometimes create a Puppet::Pops::Loader::TypedName that starts with an uppercase letter. When this name is used in order to find a type generated with puppet generate types, it isn't found. Since it's not found, a load of the Ruby type is performed instead, which results in an "Attempt to redefine entity" error when that a successful load of the generated type has been performed earlier (with a TypedName that didn't start with an uppercase letter).

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              thomas.hallgren Thomas Hallgren
              Eric Delaney Eric Delaney
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support