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

Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.6.0
    • Component/s: None
    • Labels:
      None
    • Environment:

      All platforms, installing latest build of PE 2016.3

    • Template:
    • Story Points:
      2
    • Sprint:
      Language 2016-08-10

      Description

      • tl;dr: Puppet commit b6b7ae4 looks to have caused a regression in resource type loading, or uncovered an issue elsewhere in the PE stack.

      Last night, the monolithic smoke integration pipeline failed on basic puppet enterprise installs with the following error:

       2016-07-27 01:38:19,124 - [Error]: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Resource type not found: Puppet_enterprise::Trapperkeeper::Orchestrator
        at /opt/puppetlabs/server/data/enterprise/modules/puppet_enterprise/manifests/profile/orchestrator.pp:60:15
        at /opt/puppetlabs/server/data/enterprise/modules/pe_install/manifests/install.pp:70
        on node v0f4grv1uu3a2dt.delivery.puppetlabs.net
          * /opt/puppetlabs/puppet/bin/puppet enterprise configure  --detailed-exitcodes --modulepath /opt/puppetlabs/server/data/enterprise/modules
          * returned: 1
      

      This is easily reproducible by downloading and attempting to run the installer on this build of PE 2016.3.

      I ran the installer on this same build with Puppet commit b6b7ae4 reverted, and the Trapperkeeper::Orchestrator type is loaded successfully. Thus, this auto-loading of pp-defined resource types change seems to be the issue here.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              whopper William Hopper
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support