Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-11138

puppet-firewall : Recieveing 500 error after 3.0.2 upgrade.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: firewall
    • Labels:
      None
    • Environment:

      Puppet Server   - 6.16.0 (Ubuntu 18.04; amd64)
      Puppet Client    - 6.17.0 (Ubuntu 18.04; amd64)
      Firewall Module -  3.0.2

    • Template:
      MODULES Bug Template
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: 3.0.2
      Puppet Version: 6.17.0
      OS Name/Version: Ubuntu 18.04 LTS (amd64)

      Describe your issue in as much detail as possible...

      Desired Behavior:

      The puppet catalog would apply without issue.

      Actual Behavior:

      After upgrading to the version 3.0.2, I'm getting the following error on catalog apply:

      Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Type-Name, Could not autoload puppet/type/firewall: undefined method `fact' for Facter:Module (file: /etc/puppetlabs/code/environments/production/manifests/site.pp, line: 16, column: 1) on node <machine name here>.
      

       
      The line in site.pp that the above error is pointing to is this:

      Firewall {
        before  => Class['profile_firewall::post'],
        require => Class['profile_firewall::pre']
      }
      

      From what I can tell, this comes from the changes made to lib/puppet/type/firewall.rb. If I downgrade to v3.0.1 then the error goes away.

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              adrian.iurca Adrian Iurca
              Reporter:
              mdelaney Mike Delaney
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support