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

puppet-chocolatey : latest doesn't work with --pre installation option

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: chocolatey
    • Labels:
      None
    • Environment:

      We are using Puppet Enterprise with our own Chocolatey Simple Servers

    • Template:
      MODULES Bug Template
    • Acceptance Criteria:
      Hide

      Pre tag is passed when checking if the latest version of product is installed.

      Show
      Pre tag is passed when checking if the latest version of product is installed.
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: 3.3.0
      Puppet Version: 5.5.20
      OS Name/Version: Windows Server 2019

      Describe your issue in as much detail as possible...

      Desired Behavior: Latest version of package installed

      Actual Behavior: Only non-development packages installed.

      Puppet code:

      {{}}

      package { 'my-package':
          ensure          => 'latest',
          provider        => 'chocolatey',
          source          => $chocolatey_source,
          install_options => ['--pre'],
        }

      {{}}There is a new dev release of my-package but it is not installed. (IE the version number is 1.1.1.2-DEV and version 1.1.1.1 is installed)

      I believe it is because the check to see if the latest version is installed doesn't use the --pre flag (taken from a debug log):

      0;36mDebug: Executing 'C:\ProgramData\chocolatey\choco.exe upgrade --noop my-package -r --source https://our-choco-server.domain.com/chocolatey'

      I searched through the log and only the above appears to be relevant to the checking of which package is installed.

      If I put the latest version in the ensure field then it would be installed.

      I have also double checked that the package does exist on my choco server; I could also not see any mentions of this being fixed in a later version of the chocolatey module (on the chocolatey module page)

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            xenon8 Darren Gipson
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support