Re: [Puppet Users] Re: Announce: Ruby 2.3 update planned for puppet-agent 1.6.0

2016-08-08 Thread Garrett Honeycutt 
On 8/5/16 9:12 PM, Geoff Nichols wrote:
> 
> 
> On Friday, July 29, 2016 at 5:00:26 PM UTC-7, Geoff Nichols wrote:
> 
> Because Ruby 2.1 is approaching end-of-life (upstream bugfix support
> ended March 2016), we need to move puppet-agent to a more modern
> Ruby version.
> 
> 
> If all goes well with testing, the upcoming puppet-agent 1.6.0
> release will include Ruby 2.3.1.
> 
> 
> As an update, we found some issues during testing, so puppet-agent 1.6.0
> will NOT include Ruby 2.3.1. 
> 
> We're now targeting the Ruby 2.3 update for a later puppet-agent
> release. (We'll share more information about that timeframe as the plan
> firms up.)   
> 
> Thanks,
> Geoff
> 

Hi Geoff,

It seems that the testing is leaving out the huge dataset of modules
from the Forge. Checked out the TravisCI configs for a couple of the top
supported modules including stdlib, apache, ntp, apt and vcsrepo and
none of them are testing with ruby 2.3. Suggest that before moving to a
new version of ruby, the TravisCI configs for all supported modules
should be explicitly testing against the new ruby version to ensure it
works.

For those curious about adding support for ruby 2.3.1, here's an example
TravisCI config.

https://github.com/ghoneycutt/puppet-module-ssh/blob/master/.travis.yml

Best regards,
-g


-- 
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e047976c-7f82-30c9-3631-ae8ba081ca0f%40garretthoneycutt.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: puppet lvm module

2016-08-08 Thread Alex Samad 
Hi

Sorry new to puppet, not sure which mechinism your talking about.

from the file listing

find modules/lvm/ | grep -i filesy
modules/lvm/lib/puppet/type/filesystem.rb
modules/lvm/lib/puppet/provider/filesystem
modules/lvm/lib/puppet/provider/filesystem/lvm.rb
modules/lvm/lib/puppet/provider/filesystem/aix.rb
modules/lvm/spec/unit/puppet/type/filesystem_spec.rb
modules/lvm/spec/unit/puppet/provider/filesystem
modules/lvm/spec/unit/puppet/provider/filesystem/lvm_spec.rb
modules/lvm/spec/unit/type/filesystem_spec.rb

I presume the ./lib directory is what is injecting it into the system

what do i look up in the documents to learn more about this ?


On 8 August 2016 at 23:14, jcbollinger  wrote:
>
>
> On Monday, August 8, 2016 at 2:38:35 AM UTC-5, Alex Samad wrote:
>>
>> So it seems like i can access it as just filesystem
>>
>> Why is that, i presume it comes from the puppet/lvm module ???
>
>
> Custom types are implemented via the same mechanisms that the types included
> in the base package are implemented, and that mechanism has always provided
> a single, flat namespace for all types.  There are technical challenges to
> changing the current implementation in that regard, though I'm sure those
> could be overcome if there were sufficient motivation.  In any case, all
> types implemented as native types belong to the top scope, whether they are
> included in the base Puppet distribution or not.  You'll see this with other
> modules, too, such as the stdlib's file_line.
>
>
> John
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/1-M_qx9dR2U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/b9a93808-1863-4ce3-bc0a-94af33127574%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJ%2BQ1PWpmmCh5iZwC8-WY0NWvLTVt5UMb9-G_OUD-pOTjY8%3DLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to refer to exported resource parameters in a template

2016-08-08 Thread Matthew Pounsett 


On Monday, 8 August 2016 14:02:39 UTC-7, Christopher Wood wrote:
>
> On Mon, Aug 08, 2016 at 11:28:55AM -0700, Matthew Pounsett wrote: 
> >I'm using puppet 4.4.1.  I have a case where I need the IP addresses 
> of 
> >all the servers that fit a certain set of criteria to appear in a 
> YAML 
> >list in a config file on a particular host. 
>
> Been there for an activemq.xml config file, ended up using Erik Dalén's 
> puppetdbquery. 
>
> https://forge.puppet.com/dalen/puppetdbquery 
>

That looks like it quite neatly solves the problem.
Thanks!

 

>
> This in a manifest: 
>
> $qf = query_facts('id=root', ['owner', 'datacenter']) 
>
> This in a template used in that manifest: 
>
> <% 
> list = {} 
> @qf.values.each do |h| 
>   if h['owner'] 
> owner = h['owner'] 
> list[owner] = 1 
>   end 
>   if h['datacenter'] 
> datacenter = h['datacenter'] 
> list[datacenter] = 1 
>   end 
> end 
> -%> 
>
> You get the idea, could output yaml there or whatever you wanted really. 
>
> >It seems like the first step would be to create an exported resource 
> with 
> >the required data in it, but I haven't yet found a way to refer to 
> those 
> >data from inside a template (or from inside a module in order to 
> populate 
> >a variable I can use in a template).   It seems like this would be a 
> >common pattern, but the closest examples I've been able to find are 
> for 
> >realizing the exported resource to create a file or other resource on 
> a 
> >system, rather than incorporate some of the exported resource's data 
> in 
> >other resources. 
> >How do people normally go about doing something like this?  Are there 
> some 
> >examples I've just failed to find? 
> > 
> >-- 
> >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 [1]puppet-users...@googlegroups.com . 
> >To view this discussion on the web visit 
> >[2]
> https://groups.google.com/d/msgid/puppet-users/d60d5c64-babe-4b46-8529-ceac74cf576b%40googlegroups.com.
>  
>
> >For more options, visit [3]https://groups.google.com/d/optout. 
> > 
> > References 
> > 
> >Visible links 
> >1. mailto:puppet-users+unsubscr...@googlegroups.com  
> >2. 
> https://groups.google.com/d/msgid/puppet-users/d60d5c64-babe-4b46-8529-ceac74cf576b%40googlegroups.com?utm_medium=email_source=footer
>  
> >3. https://groups.google.com/d/optout 
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8eeec81b-407c-4c34-b58b-1d4352af10ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to refer to exported resource parameters in a template

2016-08-08 Thread Christopher Wood 
On Mon, Aug 08, 2016 at 11:28:55AM -0700, Matthew Pounsett wrote:
>I'm using puppet 4.4.1.  I have a case where I need the IP addresses of
>all the servers that fit a certain set of criteria to appear in a YAML
>list in a config file on a particular host.

Been there for an activemq.xml config file, ended up using Erik Dalén's 
puppetdbquery.

https://forge.puppet.com/dalen/puppetdbquery

This in a manifest:

$qf = query_facts('id=root', ['owner', 'datacenter'])

This in a template used in that manifest:

<%
list = {}
@qf.values.each do |h|
  if h['owner']
owner = h['owner']
list[owner] = 1
  end
  if h['datacenter']
datacenter = h['datacenter']
list[datacenter] = 1
  end
end
-%>

You get the idea, could output yaml there or whatever you wanted really.

>It seems like the first step would be to create an exported resource with
>the required data in it, but I haven't yet found a way to refer to those
>data from inside a template (or from inside a module in order to populate
>a variable I can use in a template).   It seems like this would be a
>common pattern, but the closest examples I've been able to find are for
>realizing the exported resource to create a file or other resource on a
>system, rather than incorporate some of the exported resource's data in
>other resources.
>How do people normally go about doing something like this?  Are there some
>examples I've just failed to find?
> 
>--
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/d60d5c64-babe-4b46-8529-ceac74cf576b%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/d60d5c64-babe-4b46-8529-ceac74cf576b%40googlegroups.com?utm_medium=email_source=footer
>3. https://groups.google.com/d/optout

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/20160808210214.GA10600%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] How to refer to exported resource parameters in a template

2016-08-08 Thread Matthew Pounsett 

I'm using puppet 4.4.1.  I have a case where I need the IP addresses of all 
the servers that fit a certain set of criteria to appear in a YAML list in 
a config file on a particular host.

It seems like the first step would be to create an exported resource with 
the required data in it, but I haven't yet found a way to refer to those 
data from inside a template (or from inside a module in order to populate a 
variable I can use in a template).   It seems like this would be a common 
pattern, but the closest examples I've been able to find are for realizing 
the exported resource to create a file or other resource on a system, 
rather than incorporate some of the exported resource's data in other 
resources.

How do people normally go about doing something like this?  Are there some 
examples I've just failed to find?





-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d60d5c64-babe-4b46-8529-ceac74cf576b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: PuppetDB 4.2.0 is now available

2016-08-08 Thread Rob Browning 

PuppetDB 4.2.0 - Aug 08, 2016
===

PuppetDB 4.2.0 is a backward-compatible feature release that adds a
new inventory endpoint, the ability to query structured data (like
facts and resource parameters) using a dotted notation, and the
ability to trigger background/GC tasks manually via POST. This release
also includes several new queryable fields, bugfixes, and faster
retries for common error scenarios.

PuppetDB 4.2.0 Downloads


Available in native package format as part of Puppet Collection 1
(PC1). More information on the PC1 repositories is available here:
https://bit.ly/1MpEieG

Binary tarball: https://downloads.puppetlabs.com/puppetdb/

Source: https://github.com/puppetlabs/puppetdb

Please report feedback via the Puppet Labs tickets site, using an
affected PuppetDB version of 4.2.0:
https://tickets.puppetlabs.com/browse/PDB

Documentation: https://docs.puppetlabs.com/puppetdb/4.2/

Puppet module: https://forge.puppetlabs.com/puppetlabs/puppetdb

PuppetDB 4.2.0 Release Notes


Please consult the release notes here:
https://docs.puppetlabs.com/puppetdb/4.2/release_notes.html

Contributors


Andrew Roetker, Brian Cain, Eric Sorenson, Geoff Nichols, Karel
Březina, Ken Barber, Michal Bryxí, Molly Waggett, Rob Browning,
Russell Mull, Ryan Senior, and Wyatt Alt

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/87bn13dndh.fsf%40yaga.corp.puppetlabs.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Service entry for puppet agents not working

2016-08-08 Thread Bret Wortman 
The affected node (or, at least, the one I'm looking at) doesn't actually
have rundir set. The hunt for a rational explanation and ideal solution
goes on. :-)

Thanks, Rob!



*Bret Wortman*
http://wrapbuddies.co/


On Mon, Aug 8, 2016 at 12:07 PM, Rob Nelson  wrote:

>
> On Mon, Aug 8, 2016 at 11:09 AM, Bret Wortman 
> wrote:
>
>> Yep, it's not finding the pidfile because the init script is looking in
>> /var/run/puppet/agent.pid and the daemon is putting it at
>> /var/lib/puppet/run/agent.pid. So for now I'm going to modify the init
>> script wherever we are having this problem.
>
>
> We saw this issue when we performed an upgrade and the puppet.conf file's
> rundir was different than where the services file was looking for the .pid
> file. The recommendation was to remove the rundir setting from puppet.conf,
> as the default location was the same as what the service file expected,
> rather than to hardcode it to the correct value, in case it changed in the
> future.
>
>
> Rob Nelson
> rnels...@gmail.com
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/puppet-users/HC2knEe4HKw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/CAC76iT-%2BkkFUeB3W%2BGwfmMyqW6-
> tGJuhbESnj8txJCRZpSQcWw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN9oxgRfY2pANUDyGYnkmQkoFHcN2ZzcaTfbKpp09d3_Pd3L-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Service entry for puppet agents not working

2016-08-08 Thread Rob Nelson 
On Mon, Aug 8, 2016 at 11:09 AM, Bret Wortman  wrote:

> Yep, it's not finding the pidfile because the init script is looking in
> /var/run/puppet/agent.pid and the daemon is putting it at
> /var/lib/puppet/run/agent.pid. So for now I'm going to modify the init
> script wherever we are having this problem.


We saw this issue when we performed an upgrade and the puppet.conf file's
rundir was different than where the services file was looking for the .pid
file. The recommendation was to remove the rundir setting from puppet.conf,
as the default location was the same as what the service file expected,
rather than to hardcode it to the correct value, in case it changed in the
future.


Rob Nelson
rnels...@gmail.com

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAC76iT-%2BkkFUeB3W%2BGwfmMyqW6-tGJuhbESnj8txJCRZpSQcWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Service entry for puppet agents not working

2016-08-08 Thread Bret Wortman 
Yep, it's not finding the pidfile because the init script is looking in 
/var/run/puppet/agent.pid and the daemon is putting it at 
/var/lib/puppet/run/agent.pid. So for now I'm going to modify the init 
script wherever we are having this problem.

We're upgrading the systems as we update them to Centos7.

I don't know what it is about the environment that's different. That'll be 
an investigation for another day. The change to cron was basically to 
spread out our agent communication load throughout the hour (we were only 
having them check in hourly -- for us, that's plenty). This started as a 
way to figure out if there was somehow something different in the 
environments. I think there is. Just need to figure out what it is now.

Thanks!


On Monday, August 8, 2016 at 8:40:24 AM UTC-4, Bret Wortman wrote:
>
> We've been using cron to manage our puppet agents for the past few years 
> but have discovered some issues where it's running under a different 
> environment and is having trouble completing when run in cron, but it works 
> fine as a daemon or from the command line. So I'm preparing to switch over.
>
> Unfortunately, the following doesn't work for my 3.8.6 agents on Centos 6 
> systems even though it works fine for 4.3 agents:
>
> service { "puppet":
> ensure => running,
> enable => true,
> hasstatus => true,
> hasrestart => true,
> }
>
>
> What we see on some agents is that puppet will restart the service each 
> and every time it runs, which gives us lots of false "changes".
>
> # service puppet status
> puppet dead but pid file exists
> # ps aux | grep puppet | grep agent
> root  9879  0.0  0.0 134404 43516 ?   Ss 12:220:00 
> /usr/bin/ruby/usr/bin/puppet agent
>
>
> Has anyone else seen this or know of a workaround? I've tried various ways 
> of providing a "status => " command but haven't found anything that works 
> yet.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4affc1bf-5721-4883-822f-61e9e007c162%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Service entry for puppet agents not working

2016-08-08 Thread Christopher Wood 
On Mon, Aug 08, 2016 at 05:40:24AM -0700, Bret Wortman wrote:
>We've been using cron to manage our puppet agents for the past few years
>but have discovered some issues where it's running under a different
>environment and is having trouble completing when run in cron, but it
>works fine as a daemon or from the command line. So I'm preparing to
>switch over.

This sounds like an xy problem. Your underlying issue is that the agent 
sometimes runs under a different environment than desired and you'd like this 
to stop.

Over here we've had agents (3 and 4) running from cron with the following:

usecacheonfailure = false
environment = (whatever that is)

I presume that if we used the cache on failure then if the agent did not 
retrieve a catalog after an environment change in the ENC then it would perform 
the agent run with a catalog from an undesired environment.

Do you set an environment in your External Node Classifier? If not, and you 
don't specify the environment in puppet.conf then you will start in the 
'production' environment which may not be what you want.

Have you been able to narrow down and reproduce the conditions under which your 
agent runs happen in an undesired environment? You could have a different 
issue, albeit that I never had your issue in 3.8.6 with multiple environments.

NB, xy problem: http://www.perlmonks.org/?node=XY+Problem

>Unfortunately, the following doesn't work for my 3.8.6 agents on Centos 6
>systems even though it works fine for 4.3 agents:
> 
>  service { "puppet":
>      ensure => running,
>      enable => true,
>      hasstatus => true,
>      hasrestart => true,
>  }
> 
>What we see on some agents is that puppet will restart the service each
>and every time it runs, which gives us lots of false "changes".

Off hand this sounds like the service checker can't find the pid file. If it 
happens some measurable times per day in your place I would crank up the debug 
logging and see what's going on.

On the other hand, if it works in 4.3, why not upgrade the remaining 3.x agents 
and call it a day? We've had fewer issues in 4 than we had in 3.

>  # service puppet status
>  puppet dead but pid file exists
>  # ps aux | grep puppet | grep agent
>  root      9879  0.0  0.0 134404 43516 ?       Ss     12:22    0:00
>  /usr/bin/ruby/usr/bin/puppet agent
> 
>Has anyone else seen this or know of a workaround? I've tried various ways
>of providing a "status => " command but haven't found anything that works
>yet.
> 
>--
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/5ae7de27-705f-4856-aa07-68449af7385a%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/5ae7de27-705f-4856-aa07-68449af7385a%40googlegroups.com?utm_medium=email_source=footer
>3. https://groups.google.com/d/optout

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/20160808141314.GA1149%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet lvm module

2016-08-08 Thread jcbollinger 


On Monday, August 8, 2016 at 2:38:35 AM UTC-5, Alex Samad wrote:
>
> So it seems like i can access it as just filesystem 
>
> Why is that, i presume it comes from the puppet/lvm module ???
>

Custom types are implemented via the same mechanisms that the types 
included in the base package are implemented, and that mechanism has always 
provided a single, flat namespace for all types.  There are technical 
challenges to changing the current implementation in that regard, though 
I'm sure those could be overcome if there were sufficient motivation.  In 
any case, all types implemented as native types belong to the top scope, 
whether they are included in the base Puppet distribution or not.  You'll 
see this with other modules, too, such as the stdlib's file_line.


John

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b9a93808-1863-4ce3-bc0a-94af33127574%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Service entry for puppet agents not working

2016-08-08 Thread Bret Wortman 
We've been using cron to manage our puppet agents for the past few years 
but have discovered some issues where it's running under a different 
environment and is having trouble completing when run in cron, but it works 
fine as a daemon or from the command line. So I'm preparing to switch over.

Unfortunately, the following doesn't work for my 3.8.6 agents on Centos 6 
systems even though it works fine for 4.3 agents:

service { "puppet":
ensure => running,
enable => true,
hasstatus => true,
hasrestart => true,
}


What we see on some agents is that puppet will restart the service each and 
every time it runs, which gives us lots of false "changes".

# service puppet status
puppet dead but pid file exists
# ps aux | grep puppet | grep agent
root  9879  0.0  0.0 134404 43516 ?   Ss 12:220:00 
/usr/bin/ruby/usr/bin/puppet agent


Has anyone else seen this or know of a workaround? I've tried various ways 
of providing a "status => " command but haven't found anything that works 
yet.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5ae7de27-705f-4856-aa07-68449af7385a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppetserver custom mount Error 400

2016-08-08 Thread 'Josh Sinfield' via Puppet Users 
Hi Chet,
As Rob has stated - make sure the user that the Puppet master process is 
running as has permission to read + execute.

Cheers,
Josh

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e8f108a8-c62f-40f3-ad51-28bc3c7d1c54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet lvm module

2016-08-08 Thread Alex Samad 
So it seems like i can access it as just filesystem 

Why is that, i presume it comes from the puppet/lvm module ???



On Monday, 8 August 2016 17:11:50 UTC+10, Alex Samad wrote:
>
> Hi
>
> is it possible to access the filesystem type in the puppet/lvm module.
>
> in my module I tried doing this
>
>  lvm::filesystem { '/dev/vg_data/varlogyb':
> ensure => true,
> fs_type => 'ext4',
> options => '-L  varlogyb',
>   }
>
> but that errored out 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3e61aa0f-2e21-4e2f-9632-482be5001828%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet lvm module

2016-08-08 Thread Alex Samad 
Hi

is it possible to access the filesystem type in the puppet/lvm module.

in my module I tried doing this

 lvm::filesystem { '/dev/vg_data/varlogyb':
ensure => true,
fs_type => 'ext4',
options => '-L  varlogyb',
  }

but that errored out 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/c084ad8e-066c-42d6-85dd-f9f9b4718ac2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.