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

puppetlabs-postgresql : "no parameter named sensitive"

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • None
    • postgresql
    • Module Version: 7.0.3/7.2.0
      Puppetagentversion:   6.22.1

      Puppetmasterversion: 6.22.1

      Sles 12 Version 12.5

    • MODULES Bug Template
    • Needs Assessment
    • Needs Assessment

    Description

      Basic Info
      Module Version: 7.0.3/7.2.0
      Puppet Version: 6.22.1
      OS Name/Version: Sles 12 Version 12.5

      After update from module version 6.10.0 to 7.0.3, getting the error described in actual behaviour.
      Same goes for module version update to 7.2.0.
      Both times the puppetserver has been restarted, as stated in some community forums to apply the new module version correctly.
      Issue has been stated fixed after coming up in 7.0.2. This seems not to be the case.

      Desired Behavior:

      No errors upon runthrough with minimal setup.
      Update not breaking functionality, unless deprecated functions were used.

      Actual Behavior:

      Getting Error:
      Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'sensitive' (file: /etc/puppetlabs/code/environments/dev/modules/postgresql/manifests/server/role.pp, line: 84) on Postgresql_psql[CREATE ROLE testdb ENCRYPTED PASSWORD ****] (file: /etc/puppetlabs/code/environments/dev/modules/postgresql/manifests/server/role.pp, line: 84) on node testnode.redacted.de
      Hiera entry for the node in the attachments.

      Story:
      Module version 6.10.0 working as intended, specified modules coming up with the error.
      Since the error is known in 7.0.2 and was stated to be patched: newest version 7.2.0 should no have this error anymore.

      Attachments

        Activity

          People

            Unassigned Unassigned
            zilchms Markus Zilch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support