I am running into an odd issue in Puppet 4.8.0 running under Foreman 1.13.2
When, on the master, I run *puppet master --verbose --compile
myserver.domain.com *I get an error on basic facts with "Unknown Variable".
I have had this happen on multiple classes.
puppet master --verbose --compile m
age' type do its job
> rather than writing more complicated code and conditional, and protects you
> if somehow that package is uninstalled - puppet will enforce the desired
> state and re-install the package and configuration.
>
> Does that make sense?
>
>
> Rob Nels
h => /etc/pam.d/additional.conf,
> contents => template('profile/pam/additional.conf.erb'),
> }
>
> This would install the package 'pam-additional-module', then install a
> configuration file for it based on an ERB template. Just an example you can
> adapt
I am moving from Puppet 0.25 to Puppet 4. In doing so I am re-writing a
lot of the modules to work better than what I inherited.
So my current issue I am trying to figure out is how to update PAM
variables based on what external 3rd party authentication package we have
installed on that serve
I am still working to the HPUX provider to handle password expirations and
I have gotten the max and min password age values extracted from the OS,
but for the life of me I cannot seem to get them to assign to the
:password_max_age and :password_min_age fields in the Ruby code.
I know from look
On Wednesday, February 19, 2014 9:28:55 AM UTC-5, Johan De Wit wrote:
>
> Don't have any experience/access to hpux, but you can always show us
> the code and the rspec files.
> So we can have at least a look at it :)
>
> And multiple eyes see more then two :)
>
>
Thanks. I think I tracked
Thanks Johan and Martin. I looked at the links you sent, but this is what
I have already found and it really did not provide any new insights.
The main problem I am having is that what I put in rspec code should be
working but just does not. I have even hard-coded in a true or false
return,
Just a bit more explanation...
When I was looking for references I was only finding puppet-lint and
rspec-puppet for testing manifests, but not finding anything for writing
the spec files to test module functionality or modifications to existing
modules such as the HPUX user management.
--
features.
On Tuesday, February 18, 2014 7:56:51 PM UTC-5, HPUX_PUPPET wrote:
>
> I am trying to get puppet to support HPUX better than it does now so it
> can manage user accounts properly. I have already contributed changes to
> the HPUX module to change passwords, but writing
I am trying to get puppet to support HPUX better than it does now so it can
manage user accounts properly. I have already contributed changes to the
HPUX module to change passwords, but writing the rspec at the time was more
hack and guess than any real methodology. I did read the Learning Rsp
What is the best way to get a full trace of what puppet is doing, with
variable dumps and state, to troubleshoot problems like where a user's
password keeps getting reset every time puppet runs even though the
password hashes match?
I want to hack out a way to get HPUX working like we have ou
I have finally gotten Ruby 1.8.7 to compile properly with SSL libraries on
HPUX so now I am fighting how to get puppet to manage passwords.
First I modified the hpux.rb under the providers/user directory to have it
use /usr/sam/lbin/useradd.sam to add users and that worked great right off
th
12 matches
Mail list logo
