Hello,
So I am attempting to use chocolatey as a provider for puppet on my windows
machine and I am at the stage now where I am manually running manifests to
see if I am getting all the syntax correct.
I am running into a strange issue though. I have a package I created called
''rwin''. I can install it perfectly using the cinst command:
cinst rwin -source z:\software\rwin
However, when I try to install via puppet manifest
package { ''rwin'':
ensure => latest,
provider => ''chocolatey'',
source => ''Z:\Software\rwin'',
}
it appears to do nothing at all. I don''t get any error messages, it
merely
says
Notice: compiled catalog etc...
Notice: /Stage[main]//Package[rwin]/ensure: created
Notice: finished catalog etc...
And the package does not install, it does not appear under puppet resource
package.
Obviously this is my own package, so it is unlikely that anyone can
replicate the issue, but can anyone tell me how I can see what chocolatey
is doing, or what puppet is doing? The stuff spit out by --debug --verbose
and --trace is not helpful, since everything is identical to a package that
*does* work, only nothing happens. This leads me to believe it is a
chocolatey issue, especially since packages installed with the
''windows''
provider appear to work perfectly. Unfortunately I can see that something
is happening in powershell, but there is no output from the point that
puppet calls chocolatey until it returns.
I''m going to try and download a chocolatey package that I can install
from
the web and see if I can install it with an alternate source as soon as I
get back to my desk and will post the results of that.
Thanks for your help!
Jason Bray
--
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Can you run puppet with --trace --debug --verbose? My guess is that source doesn''t work with the version of the chocolatey provider that you have installed (the one on the forge needs to be updated still). On Wed, Oct 23, 2013 at 8:03 AM, Jason Bray <jbray.1982@gmail.com> wrote:> Hello, > > So I am attempting to use chocolatey as a provider for puppet on my > windows machine and I am at the stage now where I am manually running > manifests to see if I am getting all the syntax correct. > > I am running into a strange issue though. I have a package I created > called ''rwin''. I can install it perfectly using the cinst command: > > cinst rwin -source z:\software\rwin > > However, when I try to install via puppet manifest > > package { ''rwin'': > ensure => latest, > provider => ''chocolatey'', > source => ''Z:\Software\rwin'', > } > > it appears to do nothing at all. I don''t get any error messages, it merely > says > Notice: compiled catalog etc... > Notice: /Stage[main]//Package[rwin]/ensure: created > Notice: finished catalog etc... > > And the package does not install, it does not appear under puppet resource > package. > > Obviously this is my own package, so it is unlikely that anyone can > replicate the issue, but can anyone tell me how I can see what chocolatey > is doing, or what puppet is doing? The stuff spit out by --debug --verbose > and --trace is not helpful, since everything is identical to a package that > *does* work, only nothing happens. This leads me to believe it is a > chocolatey issue, especially since packages installed with the ''windows'' > provider appear to work perfectly. Unfortunately I can see that something > is happening in powershell, but there is no output from the point that > puppet calls chocolatey until it returns. > > I''m going to try and download a chocolatey package that I can install from > the web and see if I can install it with an alternate source as soon as I > get back to my desk and will post the results of that. > > > Thanks for your help! > > Jason Bray > > -- > 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+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. >-- Rob Reynolds Developer, Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
The reason for the --trace --debug --version is to see what the chocolatey provider is passing to the chocolatey tool. One suggested workaround for the forge version is to add the source to the chocolatey config. I''m not a fan of that and have added it to the provider and am working with Rich to get that into the provider and uploaded back to the forge. On Wed, Oct 23, 2013 at 1:50 PM, Rob Reynolds <rob@puppetlabs.com> wrote:> Can you run puppet with --trace --debug --verbose? > > My guess is that source doesn''t work with the version of the chocolatey > provider that you have installed (the one on the forge needs to be updated > still). > > > On Wed, Oct 23, 2013 at 8:03 AM, Jason Bray <jbray.1982@gmail.com> wrote: > >> Hello, >> >> So I am attempting to use chocolatey as a provider for puppet on my >> windows machine and I am at the stage now where I am manually running >> manifests to see if I am getting all the syntax correct. >> >> I am running into a strange issue though. I have a package I created >> called ''rwin''. I can install it perfectly using the cinst command: >> >> cinst rwin -source z:\software\rwin >> >> However, when I try to install via puppet manifest >> >> package { ''rwin'': >> ensure => latest, >> provider => ''chocolatey'', >> source => ''Z:\Software\rwin'', >> } >> >> it appears to do nothing at all. I don''t get any error messages, it >> merely says >> Notice: compiled catalog etc... >> Notice: /Stage[main]//Package[rwin]/ensure: created >> Notice: finished catalog etc... >> >> And the package does not install, it does not appear under puppet >> resource package. >> >> Obviously this is my own package, so it is unlikely that anyone can >> replicate the issue, but can anyone tell me how I can see what chocolatey >> is doing, or what puppet is doing? The stuff spit out by --debug --verbose >> and --trace is not helpful, since everything is identical to a package that >> *does* work, only nothing happens. This leads me to believe it is a >> chocolatey issue, especially since packages installed with the ''windows'' >> provider appear to work perfectly. Unfortunately I can see that something >> is happening in powershell, but there is no output from the point that >> puppet calls chocolatey until it returns. >> >> I''m going to try and download a chocolatey package that I can install >> from the web and see if I can install it with an alternate source as soon >> as I get back to my desk and will post the results of that. >> >> >> Thanks for your help! >> >> Jason Bray >> >> -- >> 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+unsubscribe@googlegroups.com. >> To post to this group, send email to puppet-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/puppet-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Rob Reynolds > Developer, Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco >-- Rob Reynolds Developer, Puppet Labs Join us at PuppetConf 2014, September 23-24 in San Francisco -- 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+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.