Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 26 2018 18:09
    @ferventcoder banned @Mikewazovsk1
tek0011
@tek0011
even better. ty
Rob Reynolds
@ferventcoder
@tek0011 when you have paying customers and have a gating issue - you turn around a fix very quickly ;)
tek0011
@tek0011
this thing you created is the best thing since <enter some nostalgic cool thing> - really awesome work. Windows has needed this since. Well. Since Windows.
Rob Reynolds
@ferventcoder
Thank you sir. The community has really helped shape it into what it is today
All we did was put in a large helping of common sense way back in the beginning
Gene Liverman
@genebean
Does anyone know why when the chocolatey package for the puppet agent updates it restarts / interrupts the network?
dragon788
@dragon788
@genebean that seems weird, does it show anything in the chocolatey.log or is there anything in the chocolateyInstall.ps1 for the agent that would trigger that?
Gene Liverman
@genebean
I hopped over to the puppet slack community and they are pointing me to some puppet tickets… I’ll post back over here in a few minutes with what they found
Gene Liverman
@genebean
It looks like this was an issue with how windows handles msi installs that Puppet resolved in https://tickets.puppetlabs.com/browse/PA-768 / versions 1.10.x
Looks like it got reported first in https://tickets.puppetlabs.com/browse/PA-663
dragon788
@dragon788
awesome, good to know!
ricou84
@ricou84
hello
i see that chocolatey/chocolatey puppet module have not been touch since july 2016? is it dead?
Rob Reynolds
@ferventcoder
Not dead, just on hold for a bit @ricou84 - did you miss the boat to switch over to puppetlabs/chocolatey? It's supported and a drop in replacement to chocolatey/chocolatey
Plus it has chocolateysource, chocolateyconfig, and chocolateyfeature
marcinbojko
@marcinbojko
And switching from chocolatey/chocolatey is painless
Gerold Katzinger
@kkzinger
are there any good workaround options while waiting on https://tickets.puppetlabs.com/browse/MODULES-4418
Rob Reynolds
@ferventcoder
Maybe comment on the issue - the more voices on those, the higher the priority
@kkzinger ^^
Gerold Katzinger
@kkzinger
done.
Louis Mayorga
@lmayorga1980
if I try to install a chocolatey package of a software that is already installed. Does chocolatey puppet will check and skip the re-installation?
Rob Reynolds
@ferventcoder
@lmayorga1980 depends on some factors (facters ;))
@lmayorga1980 first is the Chocolatey package itself. Is the package already installed or just the software?
Louis Mayorga
@lmayorga1980
just software
Rob Reynolds
@ferventcoder
So Chocolatey (and by extension the Puppet provider) are going to look at what Chocolatey has installed and go off of that.
So if the package is not also there, it will be sure to install that
now this is where it gets interesting
Louis Mayorga
@lmayorga1980
uhmmm
Rob Reynolds
@ferventcoder
If the installation script checks to see if the software is already installed and doesn't do anything, then nothing
so it would be a noop and it would be recognizing the software.
That is not built into Chocolatey itself yet, so it would have to be implemented explicitly
Louis Mayorga
@lmayorga1980
I think serverspec has a very good powershell script that checks for package on windows and if its already installed
Rob Reynolds
@ferventcoder
see https://chocolatey.org/packages/dotnet4.6.1
Louis Mayorga
@lmayorga1980
maybe something like that can be used as the base of chocolateyInstall.ps1?
Rob Reynolds
@ferventcoder
note that it checks to see if the software is already installed
Louis Mayorga
@lmayorga1980
and if you want you can force it?
Rob Reynolds
@ferventcoder
also take a look at https://chocolatey.org/packages/KB2919355#files (or any KB package for that matter) - there are two scenarios for Noop
if the software is already installed, it doesn't do anything but recognize the package installation itself (no additional software install)
and if it doesn't apply to that version of Windows it moves on (due to non-grouped dependencies per Windows version)
the other aspect you should consider is - choco sync
if you run choco sync and the package names are the same, well the package will be installed and recognized by the time you run Puppet
and note that you can make them match - https://chocolatey.org/docs/commands-sync#options-and-switches
Gerold Katzinger
@kkzinger
anyone experienced failures when updating to 0.10.9 via puppet?
currently puppet runs on my nodes keep being active with updating from 0.10.8 to 0.10.9. If I trigger a puppet run per hand via powershell the update is done without problems.
Gary Ewan Park
@gep13
@kkzinger is this when you are installing Chocolatey?
If so then yes, I believe this is a known issue that will be fixed with 0.10.0.
Basically, on initial installation we run Chocolatey once to ensure setup of config file etc, however, that initial call is exiting with a code of 1, which is being picked up with as an error.
Gerold Katzinger
@kkzinger
@gep13 Thanks for your reply. I tracked down a problem with proxy settings in my environment which could be the cause of the described behavior.
I havent tested new installations, will test this next Tuesday. Some machines are already waiting ...
Gary Ewan Park
@gep13
Gotcha! Keep us posted on how you get on.
Rob Reynolds
@ferventcoder
@kkzinger our recommendation for organizational use of Chocolatey is to shield yourself from issues that could occur like this by having Chocolatey on your INTERNAL repository and installing from there. Then subscribe to our announcements list so you'll know when we have new releases. Then you can choose when to test that and pull those things into your environment. Here is a full guide on how to get all set up properly that we've written recently (and it has scripts!): https://chocolatey.org/docs/how-to-setup-offline-installation
ssok1
@ssok1
I'm running puppet module acceptance tests and seems like i'm getting errors at puppet runs when installing choco packs