Re: [Puppet Users] Puppet Packages for Fedora 27

On Tuesday, March 6, 2018 at 11:31:26 AM UTC-8, Branan Purvine-Riley wrote:00 > We know the addition of new platforms has been lagging, and we apologize > for that. Fedora 27 is almost done, and should start appearing in our > nightly repository soon (possibly tonight, if our automated testing

[Puppet Users] mirroring puppet forge

What's the preferred way these days to internally mirror puppet forge ? I'd like to periodically catch up to current, but it doesn't have to be 'that' current, as we don't update the module versions we use too often. FWIW - we mirror things like CentOS yum repos nightly with 'reposync', but

Re: [Puppet Users] making manifest puppet 4 aware

On Thursday, January 5, 2017 at 10:37:57 AM UTC-8, Gabriel Schuyler wrote: > > Hey Vince, the $::aio_agent_version fact only exists on Puppet 4. So, > I've used its existence in the past to determine whether to use a Puppet 3 > or 4 code block. Just wrap your Puppet 4 code block in a conditiona

Re: [Puppet Users] making manifest puppet 4 aware

On Thursday, January 5, 2017 at 11:28:33 AM UTC-8, Rob Nelson wrote: > > With puppet4 showing up in vendor repos, is it safe to assume those > versions will not have an aio_agent_version fact? > > On Thu, Jan 5, 2017 at 1:37 PM, Gabriel Schuyler > wrote: > >> Hey Vince, the $::aio_agent_version f

Re: [Puppet Users] making manifest puppet 4 aware

On Thursday, January 5, 2017 at 3:49:54 AM UTC-8, Martin Alfke wrote: > You can use the fact puppetversion in you rmanifests. > > if versioncmp(‘3’, $::puppetversion) < 0 { > # puppet 4 > } else { > # puppet 3 > } > > There is no such fact on a PE 2016.4.2 client or server: aio_agent_v

[Puppet Users] making manifest puppet 4 aware

We're transitioning from PE 3.7.2 to 2016.latest and are dealing with the differences in pathnames in the new version with it putting stuff under 'code' in the tree. Is there a recommended way to make our manifests puppet-3 vs puppet-4 aware programmatically ? With the big changes in version

[Puppet Users] suppressing undefined variable warnings in PE2016.1

Is there a way to shut up the undefined variable warnings in PE2016.1 ? Here's a trivial example: # puppet apply -t --noop -e 'notice("this should print just a 'x' => x${foo}")' Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading fac

[Puppet Users] windows vs. linux version compatibility

Still confused about the great version renumbering I guess, as well as version compatibility. We have an (admittedly old) linux-hosted 3.7.x server setup ('not' enabling future parser), and want to try to manage some Windows boxes with puppet. Which package do I grab from https://downloads.pup

Re: [Puppet Users] user and service interdependencies

On Thursday, December 17, 2015 at 3:21:28 AM UTC-8, Klavs Klavsen wrote: > > Someone should really create a ticket with a suggestion to fix it (with > some examples of what this new option should fix) - and share it here - so > everyone can watch the ticket and chime in (it's open source.. rememb

[Puppet Users] slashes or dashes for module names in metadata.json ?

Confused - I've seen both used in PL docs, and both used in various tools and examples. If I'm identifying the puppetlabs stdlib into my metadata.json file as a dependency, as an example: - do I call it 'puppetlabs/stdlib' - do I call it 'puppetlabs-stdlib' - or is the story 'both are

Re: [Puppet Users] Re: custom facts sensitive to spaces

On Wednesday, September 9, 2015 at 8:27:42 AM UTC-7, Christopher Wood wrote: > There's a big "should" question here, maybe the desired behaviour needs to > be nailed down before that's a bug? > > For instance, whitespace before/after the "=" could be, according to > functionality I've seen: >

[Puppet Users] Re: custom facts sensitive to spaces

On Wednesday, September 9, 2015 at 12:01:54 AM UTC-7, Josh Cooper wrote: > I think you're running into > https://tickets.puppetlabs.com/browse/FACT-1050 > >

[Puppet Users] custom facts sensitive to spaces

I think I found a bug in facter in 3.8.2 but wanted to ask here before opening a PL ticket. Basic description is that facter has different behaviors if you run it without vs. with a fact specified. To recreate: # echo 'foo = bar' > /etc/facter/facts.d/foo.txt # facter | grep foo foo => bar #

Re: [Puppet Users] 3.8.2 can't display used licenses, can't clear bogus usage count

On Monday, August 31, 2015 at 11:43:43 AM UTC-7, Lindsey Smith wrote: > > > > On Fri, Aug 28, 2015 at 10:19 AM, Vince Skahan > wrote: > >> >>- how do I clear it back to reality ? The procedures on PL web don't >>work. >> >&

[Puppet Users] 3.8.2 can't display used licenses, can't clear bogus usage count

I'm running PE 3.8.2 and doing a lot of build/nuke/build cycles in vagrant, so I need to watch my license usage. My server currently shows 5/10 licenses used although there's only one client actually. - where is this license usage stored ? Has to be a database someplace with bogus data

[Puppet Users] puppetlabs-mysql how to create a certain grant

I'm configuring VIVO with puppet and part of the fun is creating a mysql database and doing some minimal setup. - grant all on vivo.* to ‘root’@’localhost’ identified by ‘vivo’; It's been a while since I did mysql so I'm probably not finding the secret jargon decoder ring for googling this

Re: [Puppet Users] puppetlabs-splunk doesn't appear to be future-parser compliant

On Thu, Aug 20, 2015 at 4:21 PM Vince Skahan > wrote: > On Thursday, August 20, 2015 at 3:40:59 PM UTC-7, Morgan Haskel wrote: >>> >>> Hi Vince, >>> >>> This sounds like an issue with the MODULE, could you please submit a >>> tick

Re: [Puppet Users] puppetlabs-splunk doesn't appear to be future-parser compliant

On Thursday, August 20, 2015 at 3:40:59 PM UTC-7, Morgan Haskel wrote: > > Hi Vince, > > This sounds like an issue with the MODULE, could you please submit a > ticket at https://tickets.puppetlabs.com/browse/MODULES? > > > I'd love to, but I can't complete your form successfully. The 'splunk' mo

[Puppet Users] puppetlabs-splunk doesn't appear to be future-parser compliant

Is the official supported puppetlabs-splunk module 'not' future parser compatible ? Create a foo.pp containing: class { 'splunk::forwarder': } Run puppet apply --noop with the future parser disabled - looks good... # puppet apply --noop foo.pp Notice: Compiled catalog for localhost.localdo

Re: [Puppet Users] 2015.2 strange message

On Saturday, August 15, 2015 at 5:06:09 AM UTC-7, Kylo Ginsberg wrote: > > On Thu, Aug 13, 2015 at 9:20 PM, Vince Skahan > wrote: > >> >> I'm sorry but you're going to need to reparse that one into English. >> You want me to check for what (where?) and c

Re: [Puppet Users] 2015.2 strange message

I'm sorry but you're going to need to reparse that one into English. You want me to check for what (where?) and change what (where?) ? On Thursday, August 13, 2015 at 11:44:25 AM UTC-7, Peter Huene wrote: > On Thu, Aug 13, 2015 at 10:21 AM, Vince Skahan > wrote: > >>

[Puppet Users] 2015.2 strange message

Spun up a 2015.2 system and every time an agent runs we see "Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/portage.rb: cannot load such file -- facter/util/resolution". Any ideas ? I saw one bug report at https://github.com/gentoo/puppet-portage/

Re: [Puppet Users] puppetlabs-splunk needs LOTS of usage examples

On Wednesday, July 29, 2015 at 12:28:58 PM UTC-7, Garrett Honeycutt wrote: > Sandy, > > Thanks for sharing your code! Would you consider putting in on github or > a similar place with a corresponding license. > > > I was going to write up a quick set of example docs (with attribution to the re

[Puppet Users] Re: puppetlabs-splunk needs LOTS of usage examples

On Wednesday, July 29, 2015 at 6:44:30 AM UTC-7, Christina K. wrote: > > Hi Vince, > To do that you will need to populate the > > https://github.com/puppetlabs/puppetlabs-splunk/blob/master/manifests/forwarder.pp > > forwarder_input parameter. The title won't matter so you can have 3 > differe

[Puppet Users] Re: Lucid leaving apt.puppetlabs.com

Totally agree with those sentiments.most projects have something ala 'archives.something.com' site with the historical releases. That said, you 'could' mirrror the puppetlabs stuff with reposync (or .deb equivalent) and set up your local copy to add and not delete anything... -- You recei

[Puppet Users] puppetlabs-splunk needs LOTS of usage examples

Does anybody actually use the puppetlabs-splunk module ? I've been battling this for too many hours and have a bunch of questions. I can't really find any references via Google that this is getting much usage, and the documentation in the module itself seems essentially non-existent, but I tho

[Puppet Users] Re: Puppet Enterprise 2015.2 is now available!

On Tuesday, July 28, 2015 at 9:02:34 AM UTC-7, Stephanie Stouck wrote: > The new Puppet Enterprise 2015.2 is here! We've added features to help you > deploy and move faster without sacrificing reliability, with new > capabilities to: > > I give up. I can't tell what this is. Is this the first

[Puppet Users] rpm installation ordering question and yum repos

Like many sites, we have internal yum repos that contain our internally-created rpms, as well as some other repos that are internal mirrors of upstream sites (centos updates, etc.). We're running into an ordering issue that I'm looking for what the current suggested best practice is We c

[Puppet Users] Re: how to export path in bashrc via puppet script

On Thursday, July 16, 2015 at 9:58:53 AM UTC-7, ayy...@orzota.com wrote: > > exec { file1: > command => "/bin/echo "export > JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk.x86_64"; >> /home/haas/.bashrc", > } > } > > try single quoting the inner or outer pair of quotes ?

[Puppet Users] Re: yum disable/enable repo with wildcards

On Monday, July 6, 2015 at 7:44:17 AM UTC-7, jcbollinger wrote: > Puppet provides a Yumrepo resource type for managing Yum repository >> definitions. It has an 'enabled' property, which you can set false to >> disable repos you want to keep but not use. This has the advantage that >> you no l

[Puppet Users] yum disable/enable repo with wildcards

We've set up local mirrors of a number of upstream repos, and want to point our puppet-managed boxes at the local mirrors only. Assuming we named our mirror repos local-mirror-whatever, if I was using yum on the commandline, I could do it on the fly by disabling all repos and then enabling the

[Puppet Users] Re: PL policy toward fixing known bugs in PE 3.8.x

On Thursday, June 25, 2015 at 5:49:09 PM UTC-7, Eric Sorenson wrote: > On Thursday, June 25, 2015 at 2:43:34 PM UTC-7, Vince Skahan wrote: > We absolutely do backport upstream fixes into the commercial releases, for > exactly the reasons that you describe. We do not backport *ever

[Puppet Users] PL policy toward fixing known bugs in PE 3.8.x

I'm fiddling with PE 3.8.1 to understand the pros+cons of potentially updating our 3.7.0 PE server to that as a path toward the coming soon 4.x version of PE. Unfortunately, even doing the initial module installations to 3.8.1 immediately showed issues. In this case, I ran into the error in mod

Re: [Puppet Users] Open Source 4.0 version identifier vs. very different rpm and dpkg package versions

On Tuesday, June 23, 2015 at 6:03:50 PM UTC-7, Eric Sorenson wrote: > I love metapackages too, but short of porting yum to Windows, Mac OS X, > and > Solaris I don't see how they meet those requirements. > > That's certainly reasonable. Cross-platform is hard to do. > If I¹m only doing a secu

Re: [Puppet Users] Open Source 4.0 version identifier vs. very different rpm and dpkg package versions

On Thursday, June 18, 2015 at 4:18:37 PM UTC-7, Ken Bowley wrote: > > This is better than what is currently being used, but I'm strongly in the > AIO idea to be stupid. Split it into multiple packages and use proper > dependencies like every other sane packaging system has done for a long, > lo

[Puppet Users] Re: centos 7 boxes on vagrant cloud?

On Wednesday, October 8, 2014 at 2:15:25 PM UTC-7, Scott Schneider wrote: > > I was wondering when there will be official centos 7 boxes from puppet >> labs on https://vagrantcloud.com/puppetlabs >>

Re: [Puppet Users] Open Source 4.0 version identifier vs. very different rpm and dpkg package versions

On Monday, April 27, 2015 at 2:30:00 PM UTC-7, Eric Sorenson wrote: > As an example, if it started out at puppet-agent-4.0.0 to match > puppet-4.0.0, but the only change in the next AIO package is to incorporate > a feature update in Facter (a hypothetical 2.5.0), we'd want to reflect > that fe

Re: [Puppet Users] Open Source 4.0 version identifier vs. very different rpm and dpkg package versions

On Thursday, April 23, 2015 at 3:44:35 PM UTC-7, jcf wrote: > > There is actually nothing in semver that precludes co-terming major > release versions, and less that precludes "--version" from both > displaying the local package version, AND the release number targeted by > said package if yo

[Puppet Users] Open Source 4.0 version identifier vs. very different rpm and dpkg package versions

I just set up a couple 4.0.0 virtual machines, trying to follow the installation instructions as-written on the website, and found some confusing things. First - can somebody explain why you're referring to the software in docs with one version (4.0.0) and you have a very different versioning f

Re: [Puppet Users] puppet enterprise free eval hardware requirements

On Tuesday, March 31, 2015 at 12:48:40 AM UTC-7, Brad Knowles wrote: > > When running the eval copy of PE 3.7.2 on AWS, we have found that you can > boot the master if the VM is an m3.medium (3.5GB), but you run into memory > problems that cause the system to be unreliable. If we use m3.larges

[Puppet Users] puppet enterprise free eval hardware requirements

geez puppet needs a 'lot' of oomph to spin up the first node Evaluation Environment An evaluation environment is run on a monolithic installation and is suitable for evaluating PE on 250 or fewer nodes. We recommend that your hardware meets the following: - A 4-core server with 6 GB of

[Puppet Users] puppetmaster installation instructions questions

I'm trying to set up a puppet master and client under ESXi in a home lab using Debian wheezy. Following the instructions at *https://docs.puppetlabs.com/guides/install_puppet/post_install.html#configure-a-puppet-master-server* quickly got me into a state of confusion regarding what to do. Aft

[Puppet Users] conditionally running apt-get update

In trying to spin up on puppet in a Vagrant environment, one of the things I have to do to my VM is 'apt-get update' at least once to catch the base box's understanding of what packages are where up to current. That takes a long enough time that I'd like to do it just once, or very rarely rathe