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

Chocolatey : Version is not being detected

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: chocolatey
    • Labels:
    • Template:
      MODULES Bug Template
    • Method Found:
      Needs Assessment
    • Zendesk Ticket IDs:
      39334,42661
    • Zendesk Ticket Count:
      2
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: 5.0.2
      Puppet Version: PE 2018.1.11
      OS Name/Version: Windows Server 2012 R2

      The module is not detecting the installed chocolatey version and exits with the following error:

      Failed to apply catalog: Validation of Chocolateysource[chocolatey] failed: Chocolatey version must be '0.9.9.0' to manage configuration values with Puppet. Detected '' as your version. Please upgrade Chocolatey to use this resource. (file: /etc/puppetlabs/code/environments/production/site/profile/manifests/chocolatey_client.pp, line: 20)
      

      If we run the command from the code manually, it returns the version:

      PS C:\Windows\system32> C:\ProgramData\chocolatey\choco.exe -v
      0.10.10
      

      This may be related to https://tickets.puppetlabs.com/browse/MODULES-4562

      In this case, Chocolatey for business version 0.10.10 was installed manually.

      Desired Behavior: The module should detect the version and work without error

      Actual Behavior: module is reporting the chocolatey version as ''

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              david.swan David Swan
              Reporter:
              patrick.grant Patrick Grant
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support