There seems to be a bug in the mount provider with the new puppet-agent
1.8 package. I have a node that is reporting changed file system
options every time that puppet runs although nothing is actually
changing. I downgraded back to puppet-agent 1.7.1 and this behavior
goes away.
>Notice:
On Tuesday, November 1, 2016 at 7:25:01 PM UTC, Garrett Honeycutt wrote:
> I noticed that your .fixtures.yml do not include versions. This means
> that they will always test against the latest version. You probably want
> to change this to use the version you actually use.
>
That really depe
Hi ,
Please don't open the email , It's spam somebody hacked into my email. I
have corrected the problem . Please Don't open any link from my last email
. I apologize for the inconvenience.
--Nikhil
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" g
On Fri, Oct 28, 2016 at 7:45 PM, Christopher Wood <
christopher_w...@pobox.com> wrote:
>
>
> So how would I auto-magically auto-paragraph hiera yaml to make it
> friendlier for more people, while still keeping it syntactically valid?
>
>
> Example two:
>
> ---
> one::services::enabled: true
>
> on
Thanks for reporting this Michael. Another user has reported the same in
https://tickets.puppetlabs.com/browse/PUP-6861 - we'll track the issue via
this ticket.
On Wed, Nov 2, 2016 at 6:18 AM, Michael Watters wrote:
> There seems to be a bug in the mount provider with the new puppet-agent
> 1.8
Thanks for the answer . after configuring firewall services i can able to
use * puppet agent -t*
On Wednesday, April 27, 2016 at 5:47:50 PM UTC+5:30, Karel Lenc wrote:
>
> Just for a reference, what worked for me was to reconfigure the firewall:
>
> firewall-cmd --zone=public --add-port=8140/tc
Garrett - Thanks for the heads up!
David - thanks for the comment!
I will note that I am now maintaining dependency information in 3 locations
- Puppetfile, metdata.json and .fixtures, Guess what is going to happen at
some point ;-)
Maybe I'm not aware of something, but there really should be
https://github.com/puppetlabs/puppetlabs_spec_helper/pull/107 and
https://github.com/puppetlabs/puppetlabs_spec_helper/pull/109 have partial
solutions, but never moved forward yet.
https://github.com/rnelson0/puppet-generate-puppetfile is another partial
solution.
d.
On 2 November 2016 at 16:41,
Stephen
If you're already using R10k or Librarian-Puppet, as indicated by the
Puppetfile, then it should be possible to simplify that...
For example, my .fixtures.yml looks like:
--
fixtures:
symlinks:
[module_name]: "#{source_dir}"
Puppetfile:
#!/usr/bin/env ruby
forge 'http://forge.p
On 2 November 2016 at 18:10, Gavin Williams wrote:
> Stephen
>
> If you're already using R10k or Librarian-Puppet, as indicated by the
> Puppetfile, then it should be possible to simplify that...
>
> For example, my .fixtures.yml looks like:
> --
> fixtures:
> symlinks:
> [module_name]: "#{
Dear Puppet Enterprise Users,
Puppet Enterprise 3.8.7 is now available.
This is a security and bugfix release of Puppet Enterprise. All users of
Puppet Enterprise 3.x are encouraged to upgrade when possible to Puppet
Enterprise 3.8.7. For information on the bug fixes in this release, see
https://
I recently found onceover which has a rake task to generate the fixtures,
https://github.com/dylanratcliffe/onceover#generate_fixtures, which has
some advantages over my tool currently. I think I will reach out to Dylan
to see if that can be abstracted out, as onceover may be a little
heavyweight i
12 matches
Mail list logo
