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

Global parser = future with environment.conf parser = current gives an error

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 3.8.1
    • Fix Version/s: PUP 3.8.2
    • Component/s: None
    • Labels:
    • Template:
    • Story Points:
      3
    • Sprint:
      Language 2015-07-22
    • Release Notes:
      Bug Fix

      Description

      Update


      Collect expressions in a manifest will result in an attempt to use 4.x code that has not been loaded when the parser setting is future and an environment sets parser to current. The problem does not occur if the master prior to evaluating a collexpr in a parser=current environment has evaluated something in an environment where parser=future. This can be reproduced with this manifest, having main setting parser=future, and production environment parser=current.

      node default {
        @file {'/tmp/somefile':
          content => "puppet file",
          tag => ['specialfile']
        }
       
        File <| tag == 'specialfile' |>
      }
      

      Original


      1. Set parser = future in puppet.conf
      2. Set parser = current in environment.conf for production
      3. service pe-puppetserver restart
      4. run puppet agent -t
      5. Get the following error

      [root@master381-centos ~]# service pe-puppetserver restart; puppet agent -t
      Stopping pe-puppetserver:                                  [  OK  ]
      Starting pe-puppetserver:                                  [  OK  ]
      Info: Retrieving pluginfacts
      Info: Retrieving plugin
      Info: Loading facts
      Error: Could not retrieve catalog from remote server: Error 400 on SERVER: uninitialized constant Puppet::Pops at /opt/puppet/share/puppet/modules/puppet_enterprise/manifests/profile/agent.pp:12 on node master381-centos
      Warning: Not using cache on failed catalog
      Error: Could not retrieve catalog; skipping run
      

      The issue does not occur by simply enabling future parser or by using current parser but only in this specific configuration. I think.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  nick.walker Nick Walker
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support

                      Time Tracking

                      Estimated:
                      Original Estimate - 0 minutes
                      0m
                      Remaining:
                      Remaining Estimate - 0 minutes
                      0m
                      Logged:
                      Time Spent - 30 minutes
                      30m