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

powershell : doesn't have the same semantics for exec with a timeout of 0

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • PowerShell 2.1.5
    • powershell
    • None
    • Hide
      • Documentation updated to reflect changes - 0 does not equal infinite
      • When value 0 set timeout to 300
      • When value 0 warn user
      • When value is incorrect (below lower bound, negative, character, etc) throw an error
      • Lower bound is .5 

       

      Show
      Documentation updated to reflect changes - 0 does not equal infinite When value 0 set timeout to 300 When value 0 warn user When value is incorrect (below lower bound, negative, character, etc) throw an error Lower bound is .5   
    • Windows
    • 1
    • Windows 2018-05-02, Windows 2018-05-09
    • Needs Assessment
    • Needs Assessment

    Description

      Basic Info
      Module Version: 2.1.4
      Puppet Version: N/A
      OS Name/Version: Windows

       

      With the exec resource, a timeout of 0 is allowed to mean infinite.  While the timeout value is documented in the module README, it doesn't specifically state that the value deviates from the base exec provider. There are a few options for addressing this:

      • a warning will be emitted with timeout set to `0`, with an automatic fallback to the default of `300` seconds instead
      • some notes in the docs so that it’s more clear.

      Current behavior

      • When 0 it doesn't behave as expected, a really small timeout is set.  
      • The wrong exit code may be returned

      Attachments

        Activity

          People

            Unassigned Unassigned
            ethan Ethan Brown
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support