Thanks for the detail, Rob.
I was racking my brain to compose a response with minimum success so far.
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Wa
There are times auto-loading resources from hiera data makes sense, such as
mlocal users or sudoer.d snippets (though PLEASE use .each instead of
create-resources!). These resources should absolutely be resources you in
no way manage anywhere else. For sudoer.d, you might “include sudo;
$sudoers.ea
As a trivial example maybe we suddenly found that we needed to add a
configuration file to a bunch of systems quickly. Because my coworker's
class includes a generic call to 'create_resources("file")' we can
arbitrarily add any file with any content by simply adding some data to
Hiera. Realisti
There appears to be contradiction here.
If “one-off” changes for “new functionality” are needed, why are the changes
going into a base/profile module ?
Would some more specific and detailed examples be possible ?
—
"Sometimes I think the surest sign that intellige
Hi all;
I'm a Linux engineer who went through a typical growth period with Puppet
and finally landed on the Roles and Profiles pattern which generally works
well.
I have a coworker that started on after me and doesn't like this pattern
and having to update profiles or base modules when new func
Am Dienstag, 5. Juni 2018 18:05:23 UTC+2 schrieb Josh Cooper:
>
>
>
> On Tue, Jun 5, 2018 at 8:52 AM, Sean >
> wrote:
>
>> Hello,
>>
>> I'm wanting to use the module_repository setting in puppet.conf on my
>> puppet5 master. The local repo mirror we've setup requires SSL, but has a
>> self-si
On Tue, Jun 5, 2018 at 8:52 AM, Sean wrote:
> Hello,
>
> I'm wanting to use the module_repository setting in puppet.conf on my
> puppet5 master. The local repo mirror we've setup requires SSL, but has a
> self-signed cert. Is there a way to make puppet trust that cert?
>
> Mostly, I want to be
Hello,
I'm wanting to use the module_repository setting in puppet.conf on my
puppet5 master. The local repo mirror we've setup requires SSL, but has a
self-signed cert. Is there a way to make puppet trust that cert?
Mostly, I want to be able to use puppet module search as a convenience
since
Cross-posting from Puppet Developers to get a wider audience.
Hello All,
I'm updating a module that will require a ruby gem (e.g. xml-simple) for
one of the custom providers. How does Puppet make sure that the gem is
available and installed when the module is installed? Does a *puppet module
i
On Wednesday, July 20, 2016 at 4:42:59 AM UTC-5, Tobias Koeck wrote:
>
> Hi
>
> that worked. Thanks.
>
> So if I want to force the user to set the variables in Hiera I have to use
> the hiera( .. ) function?
>
>
That's an odd way to put it, but if I understand you correctly then yes.
In other
Hi
that worked. Thanks.
So if I want to force the user to set the variables in Hiera I have to use
the hiera( .. ) function?
Greetings
Tobias
On Mon, Jul 18, 2016 at 9:11 PM, Robert Story wrote:
> On Mon, 18 Jul 2016 20:54:43 +0200 Tobias wrote:
> TK> for testing Hiera a have written a common
On Mon, 18 Jul 2016 20:54:43 +0200 Tobias wrote:
TK> for testing Hiera a have written a common.yaml with
TK>
TK> qmonitoring::db::icinga2_ido_password: "mypwd34"
TK> qmonitoring::db::icinga2_webdb_password: "mypwd544"
TK>
TK> and I have a module named qmonitoring with a class named
TK>
TK> class
You can use parameters as Rob suggests or specify the lookup yourself.
$new_var = hiera('icinga2_ido_password')
Also the var will be $::qmonitoring::db::new_var not the key you used.
I recommend matching var to lookup key to make it easier to trace
through the code.
$icinga2_ido_password = h
You should investigate hiera automatic parameter lookup (
https://docs.puppet.com/hiera/latest/puppet.html#automatic-parameter-lookup).
You need to make `icinga2_ido_password` a parameter of your class and then
APL will "magically" populate that properly. Check out the article, which
gets into deta
Hi,
for testing Hiera a have written a common.yaml with
qmonitoring::db::icinga2_ido_password: "mypwd34"
qmonitoring::db::icinga2_webdb_password: "mypwd544"
and I have a module named qmonitoring with a class named
class qmonitoring::db {
$new_var = $icinga2_ido_password,
}
where I try to aut
On 16/05/16 15:31, Harish Kothuri wrote:
Hi,
Can we customize the puppet module directory structure as i would like
to separate the puppet modules and in-house written modules.
Yes. The modulepath takes multiple entries - each should be the path to
a directory containing modules. You should fi
Harish Kothuri writes:
> Can we customize the puppet module directory structure as i would like to
> separate the puppet modules and in-house written modules.
Yes. You're looking at the 'modulepath' directive in
environment.conf:
https://docs.puppet.com/puppet/latest/reference/co
Hi,
Can we customize the puppet module directory structure as i would like to
separate the puppet modules and in-house written modules.
*Current Structure:*
/etc/puppet/environment/production/modules/ contains all modules includes
puppet forge
Ex: ntp , stdlib, chocolatey and mypackg
*Exp
So when I replace list with upgrade and specify which module within that
environment to upgrade, am I expecting that module's dependencies to be
upgraded / installed in the common modules? I ask as we got quite the
fright what that happened...
I just tested with --modulepath=environments/tools_off
/etc/puppet/modules is available for all environments (if I am not
mistaken).
--
Lowe Schmidt | +46 723 867 157
On 29 January 2016 at 10:43, James Green wrote:
> jamesg@puppet-master:/etc/puppet$ sudo puppet module list --environment
> tools_office
> /etc/puppet/environments/tools_office/modul
jamesg@puppet-master:/etc/puppet$ sudo puppet module list --environment
tools_office
/etc/puppet/environments/tools_office/modules
└── garethr-docker (v4.1.1)
/etc/puppet/modules
├── AlexCline-dirtree (v0.2.1)
├── AlexCline-fstab (v0.5.4)
[ lots of others ]
Why does puppet list the modules in the
You should probably use the gem provided with PE, not the system one.
--
Lowe Schmidt | +46 723 867 157
On 24 December 2015 at 07:14, Sandeep Majety
wrote:
>
> I am trying to intall Puppet Eneterprise in Ubuntu 14.04 machine...
>
> After running the puppet module install puppetlabs-cloud_provis
I am trying to intall Puppet Eneterprise in Ubuntu 14.04 machine...
After running the puppet module install puppetlabs-cloud_provisioner and
testing puppet help, i am getting the below error
ubuntu@ip-172-31-19-97:~$ puppet help
Error: Could not autoload puppet/face/node/install: cannot load su
Thank you Gareth. What you state is what I was thinking. It looks like
for me Solaris 10 isn't going to have an easy option for upgrading packages
(and their dependencies) considering the environment in which I work.
--
Warron French
On Sun, Nov 29, 2015 at 7:49 AM, G
On 29 November 2015 at 03:54, Warron French wrote:
> Hello, I am working on writing my first puppet module. I am pretty skilled
> in writing complex shell (bash, ksh, sh) scripts so I have some questions in
> general about writing a thorough puppet module.
>
> I want to write a single puppet modu
Hello, I am working on writing my first puppet module. I am pretty skilled
in writing complex shell (bash, ksh, sh) scripts so I have some questions
in general about writing a thorough puppet module.
I want to write a single puppet module to support installation,
configuration and service mana
Hi Ilja,
Any reason you went with test-kitchen as opposed to beaker? i am trying to
find a comparision between the two and where one fits better? as i am
going to work with Ansible too i see that learning one tool that would work
both in Ansible, and Puppet is a plus, however i am interested to k
In this case, you can have a fact that uses the code that you posted above.
Facts are just Ruby so you can pretty much do whatever you need and return
the boolean as the fact content.
However, you may need to get a bit fancy and use a confine to ensure that
only that one node is triggering the fac
No, it is remote. I am deploying a application cluster that has some nodes
dependencies, so basically in order to execute a script in one node I need
to make sure first that the remote node is already listening on a specific
port, if that node is not listening on that port I do not want to execu
Is this the *local* host listening on that port, or some remote system?
If it's the local host, then you would want to use a fact that calls
something like netstat or ss and returns a Boolean based on the result of
that port selection. You could also return all listening ports as a Hash
and go fro
Hello,
I am writing a puppet module and I am looking into a way to have a
validation before trying to execute something in puppet.
For example:
If host is listing on port 3306 {
file { 'name':
ensure => file,
}
}
or
If host is listing on port 3306 {
include '::module::
Hi,
You're welcome to checkout our modules as well
at https://github.com/unibet/. For instance
https://github.com/unibet/puppet-vagrant.
Some details about our testing mechanics:
1. rake used to manage the project. See
https://github.com/unibet/puppet-vagrant/blob/master/Rakefile
2. puppet-lib
On 8/4/15 3:37 PM, Peter Berghold wrote:
> Is there a newer set of documents on doing Spec testing of Puppet
> modules than this link?
> https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing
>
> I am running into a brick wall getting this to work so I have to assume
> I'm doin
I've got something similar I built a while ago (and need to update again
since I'm back in the Puppet world).
Magnum: https://github.com/tehmaspc/magnum
It will help you create a new module dir with a bunch of puppet tools setup
for you - including rspec-puppet for spec testing and serverspec f
On 4 August 2015 at 20:37, Peter Berghold wrote:
> Is there a newer set of documents on doing Spec testing of Puppet modules
> than this link?
> https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing
>
> I am running into a brick wall getting this to work so I have to assume I'm
Hi Peter,
On 04 Aug 2015, at 21:37, Peter Berghold wrote:
> Is there a newer set of documents on doing Spec testing of Puppet modules
> than this link?
> https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing
>
> I am running into a brick wall getting this to work so I have
Is there a newer set of documents on doing Spec testing of Puppet modules
than this link?
https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing
I am running into a brick wall getting this to work so I have to assume I'm
doing something wrong...
--
You received this message bec
Is there a definitive guide somewhere that would guide me as to how to
write Puppet module tests? In particular I'm interested in learning how to
write a tasklist file.
I keep seeing mention of such but nothing that helps...
--
You received this message because you are subscribed to the Google
On 3/9/15 9:29 AM, James Green wrote:
> I have a need to report on the modules we have installed and for each:
>
> 1. The version installed
> 2. The latest version available to upgrade to
>
> Any ideas how to get this as I'm not seeing a "puppet module" command to
> match.
>
> [ Fairly convinced
I have a need to report on the modules we have installed and for each:
1. The version installed
2. The latest version available to upgrade to
Any ideas how to get this as I'm not seeing a "puppet module" command to
match.
[ Fairly convinced I cannot be the first to ask this too... ]
Thanks,
Ja
- Original Message -
| Trying to install the module vcsrepo with puppet, but really unsure how it
| could be done. The commandline to install it is:
| puppet module install puppetlabs-vcsrepo
| Tried to install it this way, but that didn't work:
| package { 'vcsrepo':
| ensure => install
Yes, of course I have read it. I was trying to install the module with a
puppet script instead of doing it in the commandline. The documentation
said nothing about that.
lørdag 14. februar 2015 19.52.45 UTC+1 skrev Hristo Mohamed følgende:
>
> Have you considered reading the documentation?
> htt
Have you considered reading the documentation?
https://github.com/puppetlabs/puppetlabs-vcsrepo
On Sat, Feb 14, 2015 at 5:37 PM, Bilal Ahmad wrote:
> Trying to install the module vcsrepo with puppet, but really unsure how it
> could be done. The commandline to install it is:
>
> puppet module in
Trying to install the module vcsrepo with puppet, but really unsure how it
could be done. The commandline to install it is:
puppet module install puppetlabs-vcsrepo
Tried to install it this way, but that didn't work:
package { 'vcsrepo':
ensure => installed,
}
--
You receive
Question is the goal of the factor output. From my point of view, only CVEs
not implemented in the system are relevant (i.e. for reporting). CVEs
already implemented are not really from interest to me. So if the standard
behavior is, only show facts with CVEs not implemented yet and show all
CVEs o
On 10/13/2014 09:23 PM, Trevor Vaughan wrote:
> Unfortunately, I very much share Felix's fear in getting swamped by
> facts. I mean, there are *thousands* of CVEs.
Yeah, but then...
> > Would it be possible to side-load this into PuppetDB?
...this made me think of blackjack. And hookers ;-)
But
Unfortunately, I very much share Felix's fear in getting swamped by facts.
I mean, there are *thousands* of CVEs.
Good goal though, I'll have to think about this.
Trevor
On Mon, Oct 13, 2014 at 12:41 PM, Garrett Honeycutt wrote:
> On 10/13/14 8:59 AM, Trevor Vaughan wrote:
> > Would it be poss
On 10/13/2014 06:36 PM, Garrett Honeycutt wrote:
> Hi Felix,
>
> I agree this should be configurable, though I'm not sure the best way to
> go about that. Facts do not take parameters, so I'm not sure what you
> mean by that.
>
> Best regards,
> -g
Good point. You *could* manage an external fact
On 10/13/14 8:59 AM, Trevor Vaughan wrote:
> Would it be possible to side-load this into PuppetDB?
>
> For instance, instead of running the full list of checks with every run
> of puppet, have a cron job (or something) that runs the list and feeds
> the data directly into PuppetDB for the node.
>
On 10/12/14 5:16 PM, Felix Frank wrote:
> On 10/11/2014 02:22 AM, Garrett Honeycutt wrote:
>> We could check if a file exists in a directory and if so, skip the fact.
>>
>> Suggest using /usr/local/etc/cve/
>>
>> What do you think?
>
> Sure, some thing in the file system.
>
> I suggest to not har
Would it be possible to side-load this into PuppetDB?
For instance, instead of running the full list of checks with every run of
puppet, have a cron job (or something) that runs the list and feeds the
data directly into PuppetDB for the node.
That would take the pressure off of each Puppet run bu
On 10/11/2014 02:22 AM, Garrett Honeycutt wrote:
> We could check if a file exists in a directory and if so, skip the fact.
>
> Suggest using /usr/local/etc/cve/
>
> What do you think?
Sure, some thing in the file system.
I suggest to not hard code locations. This should be a parameter.
Cheers,
On 10/10/14 8:07 PM, Jeremy T. Bouse wrote:
> Granted I haven't completed taking a good look at the code yet, but to
> address Felix's concerns. What about a method of caching successful (ie:
> non-vulnerable) CVE fact results for an administratively configured
> time? This could limit the nu
On 10/10/14 7:23 PM, Felix Frank wrote:
> Hi Garrett,
>
> cool idea. I think it could use a dial to explicitly whitelist the facts
> that I want to be populated. Deploying an ever growing range of
> (sometimes expensive) checks to all agents, all of which will forever
> return false after patching
Granted I haven't completed taking a good look at the code yet, but to
address Felix's concerns. What about a method of caching successful (ie:
non-vulnerable) CVE fact results for an administratively configured
time? This could limit the number of facts that have to run through
their logic
Hi Garrett,
cool idea. I think it could use a dial to explicitly whitelist the facts
that I want to be populated. Deploying an ever growing range of
(sometimes expensive) checks to all agents, all of which will forever
return false after patching, is not a merry perspective.
What do you think?
C
Hello,
Published puppet-module-cve[1] to act as a framework for adding facts
for specific CVE's that tell you if you are vulnerable to them.
Inspiration came after ShellShock where I saw people had written modules
with corresponding facts exclusively for that exploit. Our community
needs a simple
Hi,
Just did some tests with the suggestions;
class oracle_t {
include oracle_t::install
include oracle_t::sysctl
}
class oracle_t::install {
package { 'oracle-rdbms-server-11gR2-preinstall':
ensure => present,
}
}
class oracle_t::sysctl {
sysctl { 'kernel.shmall':
ensure =
Does anyone have a module or example puppet code for turning on SNMP server
and setting the community on a Windows 2012 server?
Matt
--
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 i
Hi John/Felix,
thanks for the suggestions, will try them out next week and come back with
the results
Stefan
--
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
On 06/19/2014 02:12 PM, Stefan Heijmans wrote:
> class oracle_t {
> include install, sysctl
> }
FWIW, I consider this bad form.
You should qualify your class names, even if you include inside the same
module.
include oracle_t::install
include oracle_t::sysctl
It's not much more to type, and i
Hi,
the difference is in the /etc/sysctl.conf;'
Puppet module with all resources in 1 file
===
After; /etc/sysctl.conf
-rw-r--r--. 1 root root 2679 Jun 19 12:54 /etc/sysctl.conf
fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.core_uses_pid = 1
kernel
On 06/19/2014 02:12 PM, Stefan Heijmans wrote:
> Puppet module with all resources in 1 file
> ===
> ...
> kernel.sem is available in /etc/sysctl.conf
> kernel.sem = 250 32000 100 128
> kernel.shmall is available in /etc/sysctl.conf
> kernel.shmall = 107374182
Hello,
I've got 'something strange' with a Puppet module, using augeasproviders
(v1.2.0 or master branch of today) on Puppet 3.6.2
Below a stripped version of it with the same results as the full version;
It installs an Oracle preinstall rpm which also updates /etc/sysctl.conf
settings and us
Hi All,
I got this fully working yesterday on CentOS 6.5 and uploaded it to github
today:
https://github.com/ITBlogger/puppet-kvm
It's very crude, doesn't have any parameter validation or testing and
requires hiera as written, but you may find it useful.
At some point it would be interesting
I'm using 0022 on no both desktop and puppet master.
- Trey
On Apr 21, 2014 2:02 PM, "Robin Bowes" wrote:
> What umask are you using?
>
> R.
> On 21 Apr 2014 19:18, "treydock" wrote:
>
>> I have noticed lately that on my development system (OS X) and my
>> production Puppet master (CentOS 6.5)
What umask are you using?
R.
On 21 Apr 2014 19:18, "treydock" wrote:
> I have noticed lately that on my development system (OS X) and my
> production Puppet master (CentOS 6.5) that when installing puppet modules
> using librarian-puppet the permissions of some modules and files is very
> restri
I have noticed lately that on my development system (OS X) and my
production Puppet master (CentOS 6.5) that when installing puppet modules
using librarian-puppet the permissions of some modules and files is very
restrictive to the point where the puppetmaster can't read the files. Some
module
Thanks for pointing this out!
The problem is that one of the spec files
(spec/acceptance/nodesets/default.yml) is a symlink to another .yml file in
that directory (usually centos-64-x64.yml). The `puppet module install`
command downloads the tarball to a cache directory in /var, extracts, then
mov
On a CentOS 6.5 64-bit systems with Puppet 3.4.3 from the PuppetLabs repo:
# puppet module install puppetlabs/firewall
Notice: Preparing to install into /etc/puppet/modules ...
Notice: Downloading from https://forge.puppetlabs.com ...
Notice: Installing -- do not interrupt ...
Error: No such file
(also inline)
On 3 Mar 2014, at 19:25, Christopher Wood wrote:
> (inline)
>
> On Mon, Mar 03, 2014 at 06:24:47PM +, Robin Bowes wrote:
>>
>> Additionally, it creates two places in which the parameters can be
>> automatically set. eg. ntp::install::package_name and
>> ntp::params::
(inline)
On Mon, Mar 03, 2014 at 06:24:47PM +, Robin Bowes wrote:
>Hi Christopher,
>On 3 Mar 2014, at 17:55, Christopher Wood <[1]christopher_w...@pobox.com>
>wrote:
>
> We could have been talking in my cube. My points when I'm discussing
> this with coworkers generally
Hi Christopher,
On 3 Mar 2014, at 17:55, Christopher Wood wrote:
> We could have been talking in my cube. My points when I'm discussing this
> with coworkers generally go like so...
>
> If you use this:
>
> class { name: }
>
> You will only be able to declare that name once. If you declare c
We could have been talking in my cube. My points when I'm discussing this with
coworkers generally go like so...
If you use this:
class { name: }
You will only be able to declare that name once. If you declare classes like
this:
include ::name
include ::name::otherclass
Then you will be able
We're currently arguing^w discussing the use of the params class in
conjunction with hiera lookups and we've arrived at what I think is a
pretty good pattern. Let me explain by way of example, using the venerable
ntp application
class ntp{
include ::ntp::params
Class['::ntp::params']->
cl
On 1 March 2014 09:38, Gareth Rushgrove wrote:
> On 28 February 2014 10:20, Craig Dunn wrote:
>>
>> The main difference between Gareth's current params.pp and the 'defaults.pp'
>> model I was suggesting is that in the Gareth's pattern the params class is
>> inherited by the base class, and all th
On 28 February 2014 10:20, Craig Dunn wrote:
>
> The main difference between Gareth's current params.pp and the 'defaults.pp'
> model I was suggesting is that in the Gareth's pattern the params class is
> inherited by the base class, and all the component subclasses reference the
> variables expli
Ok, I think we are talking about the same thing, then:
https://github.com/stdmod/puppet-skeleton-standard/blob/develop/manifests/init.pp.erb
should follow what you described as defaults.pp patterns , just it uses a
class named params and not default.
On Friday, February 28, 2014 11:20:57 AM UTC+
The main difference between Gareth's current params.pp and the
'defaults.pp' model I was suggesting is that in the Gareth's pattern the
params class is inherited by the base class, and all the component
subclasses reference the variables explicitly in the scope of
base::params eg:
service { $<
Craig,
Not sure to have understood the difference between a defaults.pp pattern
and a params.pp pattern, given that I suppose that if there were parameters
in the main module class of Gareth's example they would inherit values in
params.pp exactly as the defaults example you've written.
Can be e
This is cool, though I realise that it's a (self confessed) opinionated
module design, the only thing that really stands out for me is that it
follows a rather old, and limited, 'params.pp' pattern. There is no place
for Hiera in this model without hard coding hiera lookup functions in the
classe
Hi,
I am not sure on the underlying reasons but this doesnt work under the root
account. I ran into the same issue when I was playing with it on a dev box.
Peter
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group
On Wed, Feb 05, 2014 at 06:38:24PM +0100, Gareth Rushgrove wrote:
> This came up in discussion a couple of times at the Puppet contributor
> summit at Config Management Camp in Gent over the last couple of days
> so I thought I'd write up.
>
> A while ago I put together a pretty complete/opinionat
Hi
I'm wondering if anybody has successfully managed to get any `puppet
module generate` templates (e.g.
https://github.com/garethr/puppet-module-skeleton) working on a Puppet
Enterprise box?
I've tried both of the github skeleton modules on two different versions
of PE, but not joy.
Seems strai
Thank you Gareth.
Your module skeleton has helped my module development tremendously.
Even though I created my own, differently opinionated, fork most of
the skeleton is the same and your effort is greatly appreciated.
On Wed, Feb 5, 2014 at 9:38 AM, Gareth Rushgrove
wrote:
> This came up in disc
This came up in discussion a couple of times at the Puppet contributor
summit at Config Management Camp in Gent over the last couple of days
so I thought I'd write up.
A while ago I put together a pretty complete/opinionated skeleton for
puppet modules. Especially if you're not too familiar with r
Afternoon all
I've read a fair few blogs, slideshares and other sources recently around
Module testing in Puppet, and it has spurned me on to start writing a test
framework around our internal modules... Yes, we aren't currently testing
our internal modules... Yes, we *should *be, and yes, I co
Hi,
I'm new to Puppet and having some trouble running the following commands on
my Puppet Server.
#puppet module list
or
#puppet module install puppetlabs/apt
I get the following error.
Notice: Preparing to install into /etc/puppetlabs/puppet/modules ...
Error: No source module metadata provi
On Fri, Sep 20, 2013 at 7:36 AM, Rainer Weinhold wrote:
> i just downloaded 3.3 for windows (w7,x64) and got the same error.
>
> output :
>
> C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet module install
> simondaen/iis --debug --trace
> Notice: Preparing to install into M:/.puppet/modules
On 10/8/13 2:27 PM, John wrote:
> I need to write a puppet SSHD module that does the following:
>
> First I have 5 different operating systems to install to: Red Hat, Free
> BSD, AIX, Ubuntu, and SuSE.
>
> The second requirements:
>
> If the host file contains an entry of host-A.domain.com (for
I need to write a puppet SSHD module that does the following:
First I have 5 different operating systems to install to: Red Hat, Free
BSD, AIX, Ubuntu, and SuSE.
The second requirements:
If the host file contains an entry of host-A.domain.com (for example) then
I need ssh-config1 installed.
I
i just downloaded 3.3 for windows (w7,x64) and got the same error.
output :
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet module install
simondaen/iis --debug --trace
Notice: Preparing to install into M:/.puppet/modules ...
Notice: Downloading from https://forge.puppetlabs.com ...
Error:
yes
On Thu, Sep 19, 2013 at 1:08 PM, Rob Reynolds wrote:
> Are your results of `puppet module install simondaen/iis --debug --trace`
> similar to what the others were getting?
>
>
> On Wed, Sep 18, 2013 at 1:52 PM, Samuel Huang wrote:
>
>> Yeah I rebooted, and it still didn't work.
>>
>>
>> On
Are your results of `puppet module install simondaen/iis --debug --trace`
similar to what the others were getting?
On Wed, Sep 18, 2013 at 1:52 PM, Samuel Huang wrote:
> Yeah I rebooted, and it still didn't work.
>
>
> On Monday, September 16, 2013 1:40:34 PM UTC-7, Rob Reynolds wrote:
>
>> Yes
Yeah I rebooted, and it still didn't work.
On Monday, September 16, 2013 1:40:34 PM UTC-7, Rob Reynolds wrote:
>
> Yes, that is the one that I meant. I know you hate hearing this question,
> but did you reboot after you removed it (prior to module install) for full
> effect?
>
>
> On Mon, Sep 16
Yes, that is the one that I meant. I know you hate hearing this question,
but did you reboot after you removed it (prior to module install) for full
effect?
On Mon, Sep 16, 2013 at 1:24 PM, Samuel Huang wrote:
> If what you mean by Machine store is the Local Computer, I just deleted it
> from b
Can you determine if the cert is also under Machine certificate store and
not just the Current User certificate store?
On Fri, Sep 13, 2013 at 1:27 AM, Samuel Huang wrote:
> I deleted the cert you mentioned *(thatwte-timestamping.png)*, but I
> still have the same error everyone's been mentioni
Hi,
I'm looking into writing proper modules and starting off with "puppet
module generate" but it seems the tool uses an invalid name for the
directory.
When i specify "mymodule" as a name it tells me I need to use a dash
separated name and when I use "myname-mymodule" then the module
gets gener
For what it's worth, I had the same problem and figured out the particular
cert on Windows 7 (64bit) that was causing the issue:
--
[Subject]
CN=Thawte Timestamping CA, OU=Thawte Certification, O=Thawte,
L=
On Tue, Jul 16, 2013 at 11:19 AM, Arno den Uijl wrote:
> I thought i tried the debug and trace options but i this trace was new for
> me. I looked through the code and I think that it was caused by the fact
> that there were some certificates installed with the same name. I deleted
> some from my
1 - 100 of 188 matches
Mail list logo
