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

Firewall: after the puppet resource creation, the command line output still shows the value of ensure as 'absent'

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: firewall, supported
    • Labels:
      None

      Description

      When trying to create a firewall resource using 'puppet resource' command, the resource gets created, but the output from the command still shows the value of 'ensure' as 'absent' which is misleading.

      #puppet module install puppetlabs-firewall
      [root@nnxiotspfan5q3a ~]# ls /etc/puppetlabs/code/environments/production/modules/
      firewall
      [root@nnxiotspfan5q3a ~]# puppet resource firewall 000 ensure=present
      Notice: /Firewall[000]/ensure: created
      firewall { '000':
        ensure => 'absent',
      }
      

      A listing of the firewall resource shows the new firewall resource is present.

      [root@nnxiotspfan5q3a ~]# puppet resource firewall
      firewall { '000':
        ensure             => 'present',
        chain              => 'INPUT',
        checksum_fill      => 'false',
        clamp_mss_to_pmtu  => 'false',
        isfragment         => 'false',
        kernel_timezone    => 'false',
        physdev_is_bridged => 'false',
        proto              => 'tcp',
        random             => 'false',
        rdest              => 'false',
        reap               => 'false',
        rsource            => 'false',
        rttl               => 'false',
        socket             => 'false',
        table              => 'filter',
        time_contiguous    => 'false',
      }
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              shaigy.nixon Shaigy Nixon [X] (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support