Managing Chocolatey sources with File resource and Template on Windows 7 x64 SP1

jmp242

unread,

Sep 1, 2015, 8:50:48 AM9/1/15

to Puppet Users

So I'm using Puppet 3.8.1 on Windows 7 x64 and managing a configuration file using a template.

file { 'chocolatey.config':
        path    => "C:/ProgramData/chocolatey/config/chocolatey.config",
        content => template('yum/chocolatey.config.erb'),
        owner   => 'SYSTEM',
        group   => 'Administrators',
        mode    => '0775',
        ensure  => present,
        require => Exec['chocolatelyinstall'],
      }

The template file grabs values from a foreman parameter:

<?xml version="1.0" encoding="utf-8"?>
<chocolatey xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <cacheLocation />
  <containsLegacyPackageInstalls>true</containsLegacyPackageInstalls>
  <commandExecutionTimeoutSeconds>2700</commandExecutionTimeoutSeconds>
  <sources>
    <source id="chocolatey" value="https://chocolatey.org/api/v2/" disabled="true" />
    <source id="<%= @choco_repo_name %>" value="<%= @choco_repo_url %>" disabled="false" />
  </sources>
  <features>
    <feature name="checksumFiles" enabled="true" setExplicitly="false" />
    <feature name="autoUninstaller" enabled="true" setExplicitly="true" />
    <feature name="allowGlobalConfirmation" enabled="false" setExplicitly="false" />
  </features>
  <apiKeys />
</chocolatey>

Every time it runs, even one manual run right after another, it changes the file from one hash to a different one, always the same 2 hashes, and the contents of the file (text) are the same each time. I also get a FileBucket got a duplicate file each time.

Notice: /Stage[main]/Yum/File[chocolatey.config]/content:                       
                                                                                
Info: Computing checksum on file C:/ProgramData/chocolatey/config/chocolatey.con
fig                                                                             
Info: FileBucket got a duplicate file {md5}eedc18d21cf625bb6c04902e8a9dd409     
Info: /Stage[main]/Yum/File[chocolatey.config]: Filebucketed C:/ProgramData/choc
olatey/config/chocolatey.config to puppet with sum eedc18d21cf625bb6c04902e8a9dd
409                                                                             
Notice: /Stage[main]/Yum/File[chocolatey.config]/content: content changed '{md5}
eedc18d21cf625bb6c04902e8a9dd409' to '{md5}4efbb2600ee773122152faec7ae80934'

Any idea WTH is going on?

Rob Reynolds

unread,

Sep 2, 2015, 5:28:58 PM9/2/15

to puppet...@googlegroups.com

At first I thought it might be related to PUP-927[1], but that was "fixed" in 3.8.0. It appears that maybe it is similar to that or the fix in 3.8.0 was not enough. Is the Puppet version you have installed x86 or x64?

[1] https://tickets.puppetlabs.com/browse/PUP-927

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b51075e6-422b-4614-88db-787618d89e6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Rob Reynolds

Developer, Puppet Labs

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9.

Register now to take advantage of the Final Countdown discount —save $149!

jmp242

unread,

Sep 4, 2015, 9:25:16 AM9/4/15

to Puppet Users

64 bit.

Rob Reynolds

unread,

Sep 9, 2015, 2:26:38 PM9/9/15

to puppet...@googlegroups.com

Can you take a look at your line endings in the template file? And then determine what the line endings are in the actual chocolatey.config after choco.exe runs?

On Fri, Sep 4, 2015 at 8:25 AM, jmp242 <jp1...@gmail.com> wrote:

64 bit.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/05bd8bec-247e-44a0-870b-2936a038c41c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

jmp242

unread,

Sep 15, 2015, 2:24:40 PM9/15/15

to Puppet Users

The template file was created in Geppeto, and has crlf line endings. The chocolatey.config also has crlf line endings. This is tested using the file command on Scientific Linux 7.1. For testing the windows file, I copied it over SMB from the windows computer.

Rob Reynolds

unread,

Sep 17, 2015, 9:56:20 AM9/17/15

to puppet...@googlegroups.com

On Tue, Sep 15, 2015 at 1:24 PM, jmp242 <jp1...@gmail.com> wrote:

The template file was created in Geppeto, and has crlf line endings. The chocolatey.config also has crlf line endings. This is tested using the file command on Scientific Linux 7.1. For testing the windows file, I copied it over SMB from the windows computer.

This sounds like a possible Puppet bug. If you can get a simple repro up as a github repo (remove Chocolatey from the equation though as it changes the file), we can test it out. I created something similar once for the similar issue I mentioned (PUP-927[1]) - puppet-simple_templates[2]. Once you have a repro without chocolatey being part of the equation, create a ticket in JIRA[3] to followup. If it turns out it has something to do with Chocolatey instead, there is already have an issue not to mess with the config file if there are no changes[4], which should be fixed in 0.9.9.9.

[1] https://tickets.puppetlabs.com/browse/PUP-927

[2] https://github.com/ferventcoder/puppet-simple_templates

[3] https://tickets.puppetlabs.com/browse/PUP

[4] https://github.com/chocolatey/choco/issues/364

On Wednesday, September 9, 2015 at 2:26:38 PM UTC-4, Rob Reynolds wrote:
Can you take a look at your line endings in the template file? And then determine what the line endings are in the actual chocolatey.config after choco.exe runs?

On Fri, Sep 4, 2015 at 8:25 AM, jmp242 <jp1...@gmail.com> wrote:
64 bit.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/05bd8bec-247e-44a0-870b-2936a038c41c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
Rob Reynolds
Developer, Puppet Labs

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9.
Register now to take advantage of the Final Countdown discount —save $149!

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/040de04a-5720-4726-80d3-5203c8c80943%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Rob Reynolds

Developer, Puppet Labs

PuppetConf 2015 is right around the corner! Join us October 5-9 in Portland, OR. Register now.

Fredrik Nilsson

unread,

Oct 2, 2015, 10:31:09 AM10/2/15

to Puppet Users

Hi,

I've actually noticed the exact same behaviour, always replacing chocolatey.config and always with the same to hashes. We're running client version 3.8.3 and both x86 and x64 versions are experiencing the same error. Jmp242 did you file a bug report on this?

I compared the file before and after in Notepad++ that said it was identical so I made a nother comparison using HxD that also reported the files identical...

//Fredrik

jmp242

unread,

Oct 2, 2015, 2:55:44 PM10/2/15

to Puppet Users

Sadly, I haven't had time to figure out how to submit a bug on this. If you can, it would be great.

Rob Reynolds

unread,

Oct 4, 2015, 10:31:09 PM10/4/15

to puppet...@googlegroups.com

You folks may want to upgrade to 0.9.9.10 and see if this behavior is still observed. Chocolatey no longer touches the config file unless changes are needed[1].

[1] https://github.com/chocolatey/choco/issues/364

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b3bceba4-0b22-470f-87d1-130d8d02a194%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Fredrik Nilsson

unread,

Oct 8, 2015, 3:44:09 AM10/8/15

to Puppet Users

Let's see if I can shed some light on this. Updated to Chocolatey 0.9.10-beta1 to see if this behaviour disappears, sadly it didn't. To puppet runs back to back will result in the file getting replaced both runs. There are no "manual" chocolatey interference during those runs as they are back to back, allthough I notice quite som action in my chocolatey.log durring those runs. I'm a little uncertain if that is the normal behaviour or not as I haven't monitored this file before this issue occured. I asked my puppet master right now and he had the feeling this surfaced when we moved from agent version 3.8.1 to 3.8.3, I'm not 100% with him on that as I know there where some server updates in the same time frame. Anyhow, logs are fun so I'm gonna give you the 225 rows it logs during the normal puppet run that might cast a light on whether chocolatey or puppet is the bad guy....

chocolatey.log:

2015-10-08 08:47:56,795 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:47:56,795 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:47:56,826 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:47:57,154 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:47:57,217 [INFO ] - 0.9.10-beta1
2015-10-08 08:48:08,873 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:08,873 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:08,920 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:48:09,232 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\config\chocolatey.config.update"
to "C:\ProgramData\chocolatey\config\chocolatey.config".
2015-10-08 08:48:09,248 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:48:09,310 [INFO ] - 0.9.10-beta1
2015-10-08 08:48:10,185 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:10,185 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:10,217 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:48:10,560 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:48:10,639 [DEBUG] - Chocolatey is running on Windows v 6.3.9600.0
2015-10-08 08:48:10,639 [DEBUG] - Attempting to delete file "C:/ProgramData/chocolatey/choco.exe.old".
2015-10-08 08:48:10,639 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\choco.exe.old".
2015-10-08 08:48:10,654 [DEBUG] - Command line: "C:\ProgramData\chocolatey\choco.exe" list -lo -r
2015-10-08 08:48:10,654 [DEBUG] - Received arguments: list -lo -r
2015-10-08 08:48:10,732 [DEBUG] - The source 'https://__OUR__LOCAL__REPO__/chocolatey;https://chocolatey.org/api/v2/' evaluated to a 'normal' source type
2015-10-08 08:48:10,732 [DEBUG] -
NOTE: Hiding sensitive configuration data! Please double and triple
check to be sure no sensitive data is shown, especially if copying
output to a gist for review.
2015-10-08 08:48:10,748 [DEBUG] - Configuration: CommandName='list'|
CacheLocation='C:\Users\ADM_FR~1\AppData\Local\Temp'|
ContainsLegacyPackageInstalls='True'|
CommandExecutionTimeoutSeconds='2700'|
Sources='https://__OUR__LOCAL__REPO__/chocolatey;https://chocolatey.org/api/v2/'|

Information.Is64Bit='True'|Information.IsInteractive='True'|
Information.IsUserAdministrator='True'|
Information.IsProcessElevated='True'|Features.AutoUninstaller='True'|
Features.CheckSumFiles='True'|Features.FailOnAutoUninstaller='False'|
ListCommand.LocalOnly='True'|
ListCommand.IncludeRegistryPrograms='False'|ListCommand.PageSize='25'|
UpgradeCommand.FailOnUnfound='False'|
UpgradeCommand.FailOnNotInstalled='False'|
UpgradeCommand.NotifyOnlyAvailableUpgrades='False'|
NewCommand.AutomaticPackage='False'|SourceCommand.Command='unknown'|
SourceCommand.Priority='0'|FeatureCommand.Command='unknown'|
ConfigCommand.Command='unknown'|PushCommand.TimeoutInSeconds='0'|
PinCommand.Command='unknown'|
2015-10-08 08:48:10,748 [DEBUG] - _ Chocolatey:ChocolateyListCommand - Normal Run Mode _
2015-10-08 08:48:11,092 [INFO ] - chocolatey|0.9.10-beta-20151007
2015-10-08 08:48:11,107 [INFO ] - git|2.5.3
2015-10-08 08:48:11,107 [INFO ] - git.install|2.5.3
2015-10-08 08:48:11,107 [INFO ] - notepadplusplus.install|6.8.3
2015-10-08 08:48:11,107 [INFO ] - nscp|0.4.3.143
2015-10-08 08:48:11,107 [INFO ] - puppet|3.8.3
2015-10-08 08:48:11,107 [INFO ] - splunk-universal-forwarder|6.1.1.207789
2015-10-08 08:48:11,107 [INFO ] - warmup|0.6.5.1
2015-10-08 08:48:11,107 [INFO ] - wintail|1.17.2
2015-10-08 08:48:11,107 [DEBUG] - Exiting with 0
2015-10-08 08:48:11,654 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:11,654 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:11,701 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:48:12,264 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:48:12,326 [DEBUG] - Chocolatey is running on Windows v 6.3.9600.0
2015-10-08 08:48:12,342 [DEBUG] - Attempting to delete file "C:/ProgramData/chocolatey/choco.exe.old".
2015-10-08 08:48:12,342 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\choco.exe.old".
2015-10-08 08:48:12,342 [DEBUG] - Command line: "C:\ProgramData\chocolatey\choco.exe" upgrade --noop nscp -r
2015-10-08 08:48:12,342 [DEBUG] - Received arguments: upgrade --noop nscp -r
2015-10-08 08:48:12,420 [DEBUG] - The source 'https://__OUR__LOCAL__REPO__/chocolatey;https://chocolatey.org/api/v2/' evaluated to a 'normal' source type
2015-10-08 08:48:12,420 [DEBUG] -
NOTE: Hiding sensitive configuration data! Please double and triple
check to be sure no sensitive data is shown, especially if copying
output to a gist for review.
2015-10-08 08:48:12,451 [DEBUG] - Configuration: CommandName='upgrade'|
CacheLocation='C:\Users\ADM_FR~1\AppData\Local\Temp'|
ContainsLegacyPackageInstalls='True'|
CommandExecutionTimeoutSeconds='2700'|
Sources='https://__OUR__LOCAL__REPO__/chocolatey;https://chocolatey.org/api/v2/'|

Information.Is64Bit='True'|Information.IsInteractive='True'|
Information.IsUserAdministrator='True'|
Information.IsProcessElevated='True'|Features.AutoUninstaller='True'|
Features.CheckSumFiles='True'|Features.FailOnAutoUninstaller='False'|
ListCommand.LocalOnly='False'|
ListCommand.IncludeRegistryPrograms='False'|ListCommand.PageSize='25'|
UpgradeCommand.FailOnUnfound='False'|
UpgradeCommand.FailOnNotInstalled='False'|
UpgradeCommand.NotifyOnlyAvailableUpgrades='False'|
NewCommand.AutomaticPackage='False'|SourceCommand.Command='unknown'|
SourceCommand.Priority='0'|FeatureCommand.Command='unknown'|
ConfigCommand.Command='unknown'|PushCommand.TimeoutInSeconds='0'|
PinCommand.Command='unknown'|
2015-10-08 08:48:31,279 [INFO ] - nscp|0.4.3.143|0.4.3.143|false
2015-10-08 08:48:31,295 [DEBUG] - Exiting with 0
2015-10-08 08:48:31,998 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:31,998 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:32,045 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:48:32,451 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:48:32,654 [DEBUG] - Chocolatey is running on Windows v 6.3.9600.0
2015-10-08 08:48:32,654 [DEBUG] - Attempting to delete file "C:/ProgramData/chocolatey/choco.exe.old".
2015-10-08 08:48:32,654 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\choco.exe.old".
2015-10-08 08:48:32,670 [DEBUG] - Command line: "C:\ProgramData\chocolatey\choco.exe" feature list -r
2015-10-08 08:48:32,686 [DEBUG] - Received arguments: feature list -r
2015-10-08 08:48:32,889 [DEBUG] - The source '' evaluated to a 'normal' source type
2015-10-08 08:48:32,889 [DEBUG] -
NOTE: Hiding sensitive configuration data! Please double and triple
check to be sure no sensitive data is shown, especially if copying
output to a gist for review.
2015-10-08 08:48:32,920 [DEBUG] - Configuration: CommandName='feature'|
CacheLocation='C:\Users\ADM_FR~1\AppData\Local\Temp'|
ContainsLegacyPackageInstalls='True'|
CommandExecutionTimeoutSeconds='2700'|SourceType='normal'|
Debug='False'|
Verbose='False'|Force='False'|Noop='False'|HelpRequested='False'|
RegularOutput='False'|QuietOutput='False'|PromptForConfirmation='True'|
AcceptLicense='False'|AllowUnofficialBuild='False'|Input='list'|
AllVersions='False'|SkipPackageInstallProvider='False'|
Prerelease='False'|ForceX86='False'|OverrideArguments='False'|
NotSilent='False'|IgnoreDependencies='False'|
AllowMultipleVersions='False'|AllowDowngrade='False'|
ForceDependencies='False'|Information.PlatformType='Windows'|
Information.PlatformVersion='6.3.9600.0'|
Information.PlatformName='Windows Server 2012 R2'|
Information.ChocolateyVersion='0.9.10.0'|
Information.ChocolateyProductVersion='0.9.10-beta1'|
Information.FullName='choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb'|

Information.Is64Bit='True'|Information.IsInteractive='True'|
Information.IsUserAdministrator='True'|
Information.IsProcessElevated='True'|Features.AutoUninstaller='True'|
Features.CheckSumFiles='True'|Features.FailOnAutoUninstaller='False'|
ListCommand.LocalOnly='False'|
ListCommand.IncludeRegistryPrograms='False'|ListCommand.PageSize='25'|
UpgradeCommand.FailOnUnfound='False'|
UpgradeCommand.FailOnNotInstalled='False'|
UpgradeCommand.NotifyOnlyAvailableUpgrades='False'|
NewCommand.AutomaticPackage='False'|SourceCommand.Command='unknown'|
SourceCommand.Priority='0'|FeatureCommand.Command='list'|
ConfigCommand.Command='unknown'|PushCommand.TimeoutInSeconds='0'|
PinCommand.Command='unknown'|
2015-10-08 08:48:32,936 [DEBUG] - _ Chocolatey:ChocolateyFeatureCommand - Normal Run Mode _
2015-10-08 08:48:32,951 [INFO ] - checksumFiles - [Enabled] | Checksum files when pulled in from internet (based on package).
2015-10-08 08:48:32,951 [INFO ] - autoUninstaller - [Enabled] | Uninstall from programs and features without requiring an explicit uninstall script.
2015-10-08 08:48:32,951 [INFO ] - allowGlobalConfirmation - [Disabled] | Prompt for confirmation in scripts or bypass.
2015-10-08 08:48:32,951 [INFO ] - failOnAutoUninstaller - [Disabled] | Fail if automatic uninstaller fails.
2015-10-08 08:48:32,951 [DEBUG] - Exiting with 0
2015-10-08 08:48:33,842 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:33,842 [DEBUG] - Configured chocolatey.infrastructure.logging.log4net.config.xml from assembly choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb
2015-10-08 08:48:33,889 [DEBUG] - XmlConfiguration is now operational
2015-10-08 08:48:34,186 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:48:34,248 [DEBUG] - Chocolatey is running on Windows v 6.3.9600.0
2015-10-08 08:48:34,248 [DEBUG] - Attempting to delete file "C:/ProgramData/chocolatey/choco.exe.old".
2015-10-08 08:48:34,248 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\choco.exe.old".
2015-10-08 08:48:34,264 [DEBUG] - Command line: "C:\ProgramData\chocolatey\choco.exe" feature -r enable -n autoUninstaller
2015-10-08 08:48:34,264 [DEBUG] - Received arguments: feature -r enable -n autoUninstaller
2015-10-08 08:48:34,342 [DEBUG] - The source '' evaluated to a 'normal' source type
2015-10-08 08:48:34,357 [DEBUG] -
NOTE: Hiding sensitive configuration data! Please double and triple
check to be sure no sensitive data is shown, especially if copying
output to a gist for review.
2015-10-08 08:48:34,373 [DEBUG] - Configuration: CommandName='feature'|
CacheLocation='C:\Users\ADM_FR~1\AppData\Local\Temp'|
ContainsLegacyPackageInstalls='True'|
CommandExecutionTimeoutSeconds='2700'|SourceType='normal'|
Debug='False'|
Verbose='False'|Force='False'|Noop='False'|HelpRequested='False'|
RegularOutput='False'|QuietOutput='False'|PromptForConfirmation='True'|
AcceptLicense='False'|AllowUnofficialBuild='False'|Input='enable'|
AllVersions='False'|SkipPackageInstallProvider='False'|
Prerelease='False'|ForceX86='False'|OverrideArguments='False'|
NotSilent='False'|IgnoreDependencies='False'|
AllowMultipleVersions='False'|AllowDowngrade='False'|
ForceDependencies='False'|Information.PlatformType='Windows'|
Information.PlatformVersion='6.3.9600.0'|
Information.PlatformName='Windows Server 2012 R2'|
Information.ChocolateyVersion='0.9.10.0'|
Information.ChocolateyProductVersion='0.9.10-beta1'|
Information.FullName='choco, Version=0.9.10.0, Culture=neutral, PublicKeyToken=79d02ea9cad655eb'|

Information.Is64Bit='True'|Information.IsInteractive='True'|
Information.IsUserAdministrator='True'|
Information.IsProcessElevated='True'|Features.AutoUninstaller='True'|
Features.CheckSumFiles='True'|Features.FailOnAutoUninstaller='False'|
ListCommand.LocalOnly='False'|
ListCommand.IncludeRegistryPrograms='False'|ListCommand.PageSize='25'|
UpgradeCommand.FailOnUnfound='False'|
UpgradeCommand.FailOnNotInstalled='False'|
UpgradeCommand.NotifyOnlyAvailableUpgrades='False'|
NewCommand.AutomaticPackage='False'|SourceCommand.Command='unknown'|
SourceCommand.Priority='0'|FeatureCommand.Name='autoUninstaller'|
FeatureCommand.Command='enable'|ConfigCommand.Command='unknown'|
PushCommand.TimeoutInSeconds='0'|PinCommand.Command='unknown'|
2015-10-08 08:48:34,373 [DEBUG] - _ Chocolatey:ChocolateyFeatureCommand - Normal Run Mode _
2015-10-08 08:48:34,404 [INFO ] - autoUninstaller was enabled by default. Explicitly setting value.
2015-10-08 08:48:34,420 [DEBUG] - Attempting to copy "C:\ProgramData\chocolatey\config\chocolatey.config.update"
to "C:\ProgramData\chocolatey\config\chocolatey.config".
2015-10-08 08:48:34,420 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\config\chocolatey.config.update".
2015-10-08 08:48:34,420 [WARN ] - Enabled autoUninstaller
2015-10-08 08:48:34,420 [DEBUG] - Exiting with 0

Rob Reynolds

unread,

Oct 12, 2015, 11:08:38 AM10/12/15

to puppet...@googlegroups.com

On Thu, Oct 8, 2015 at 12:44 AM, Fredrik Nilsson <socc...@gmail.com> wrote:

Let's see if I can shed some light on this. Updated to Chocolatey 0.9.10-beta1 to see if this behaviour disappears, sadly it didn't. To puppet runs back to back will result in the file getting replaced both runs. There are no "manual" chocolatey interference during those runs as they are back to back, allthough I notice quite som action in my chocolatey.log durring those runs. I'm a little uncertain if that is the normal behaviour or not as I haven't monitored this file before this issue occured. I asked my puppet master right now and he had the feeling this surfaced when we moved from agent version 3.8.1 to 3.8.3, I'm not 100% with him on that as I know there where some server updates in the same time frame. Anyhow, logs are fun so I'm gonna give you the 225 rows it logs during the normal puppet run that might cast a light on whether chocolatey or puppet is the bad guy....

0.9.10 Beta 1 (released Oct 7) should include the fixes that went into 0.9.9.10. I did forget to mention one really important consideration about updating.

Before we get into who is the bad guy, let's make sure your template is up to date. Chocolatey WILL make changes to the file if it is not correct to the minimum of Chocolatey expects the file to have. And there have been new values added to the file for 0.9.9.9+. There was also some reordering that has occurred for the other configuration settings. So if you haven't also compensated for all of the new changes, you are likely fighting with Chocolatey every run.

So take a look at what Chocolatey now expects the file format to be, adjust your template, and then see if this is fixed. :)

Note: I have mentioned using a template is an anti-pattern for the choco config file, I know it's all you have right now. We're working on ensuring that you can do full configuration of choco from all manifests. It's not quite done yet, so I can understand a need to continue to use a template. Once that feature is complete, I will be recommending folks use that instead so there is no chance of fighting with choco anymore.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/937e7716-5a7d-4dd1-b13e-04db3308dc07%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Rob Reynolds

Developer, Puppet Labs

PuppetConf 2015 is this week! Join us via the live stream!

Fredrik Nilsson

unread,

Oct 27, 2015, 3:14:26 AM10/27/15

to Puppet Users

Should have replied earlier, to much to do I guess.

Anyways what seems to have solved the issue in our case was an update of chocolatey to the latest stable release in the form of 0.9.9.11, updating the template of the configuration handled by puppet and also updating the chocolatey puppet module, I'm unaware of the version in that case, but that quieted it all down and now we're back to business as usual...

Rob Reynolds

unread,

Oct 30, 2015, 5:37:02 PM10/30/15

to puppet...@googlegroups.com

On Tue, Oct 27, 2015 at 2:14 AM, Fredrik Nilsson <socc...@gmail.com> wrote:

Should have replied earlier, to much to do I guess.

Anyways what seems to have solved the issue in our case was an update of chocolatey to the latest stable release in the form of 0.9.9.11, updating the template of the configuration handled by puppet and also updating the chocolatey puppet module, I'm unaware of the version in that case, but that quieted it all down and now we're back to business as usual...

Great to hear!

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/9e2501d3-04d6-4943-b5ba-9e6f3c2b2391%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Reply all

Reply to author

Forward