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

puppetlabs-powershell: Powershell module breaks puppet run on linux boxes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: powershell
    • Labels:
    • Template:
      MODULES Bug Template
    • Method Found:
      Needs Assessment
    • Zendesk Ticket IDs:
      40048
    • Zendesk Ticket Count:
      1
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: v3.0.1
      Puppet Version: 6
      OS Name/Version: Centos

      When i add powershell module to an environment, it breaks Puppet run on linux hosts:

      Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: 
      Error while evaluating a Resource Statement, 
      Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/exec: 
      Could not autoload puppet/provider/exec/powershell: no such file to load -- ruby-pwsh on node xxxx.xx.xx
      

      Desired Behavior:
      Powershell module shall not break puppet run if ruby-pwsh is not available.

      Looks like powershell module with tag 3.0.1 brakes execution of puppet on out linux hosts, where we have no PowerShell nor pwsh.

      The issue was introduced in this commit: https://github.com/puppetlabs/puppetlabs-powershell/commit/31fec64da2916446527504f5a04cf8f75f59dfa0
      cc David Swan

      By default ruby rescue "StandardError", but the catch is that "LoadError" is not a subset of "StandardError"
      https://ruby-doc.org/core-2.5.0/Exception.html

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              michael.lombardi Michael Lombardi
              Reporter:
              igan Iakov Gan
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support