Confused after system upgrade - F22, Puppet 4.1.0-5

[Bret Wortman]

So I upgraded our Puppet server to Fedora 22, which brought with it an upgrade from Puppet 3.8-ish to 4.1.0-5. And as this wasn't expected (I should have read and studied more -- it's definitely my fault), a few things have confused me as I've started reading the Puppetlabs site for 4.1 documentation:

1. It says that config files are now under /etc/puppetlabs/puppet, but the RPM says it installed everything to /etc/puppet as always. Which is right?

2. My hiera config, or at least the default .yaml file I set up, isn't being seen -- I suspect this is related to #1, but could something else be to blame? The specific error when running a Puppet 4.1 client against my system (actually, the agent running on the server since this was the first F22 upgrade we did) is:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evalutaiton Error: Error while evaluating a Function Call, Could not find data item proxy in any Hiera data file and no default supplied at /path/to/manifests/site.pp:25:10 on node puppetserver.foo.net

3. Has Puppetlabs stopped providing RPMs at their yum server? I haven't seen a full set since F20.

Thanks,

Bret Wortman

[Bret Wortman]

Actually, I think my hiera problem may be rleated to this line in my hiera.yaml file:

:yaml:

  :datadir: '/etc/puppet/environments/%{environment}/data'

Since I saw that environments changed in Puppet 4.

[Martin Alfke]

Hi Bret,

On 08 Oct 2015, at 09:08, Bret Wortman <br...@thewortmans.org> wrote:

> So I upgraded our Puppet server to Fedora 22, which brought with it an upgrade from Puppet 3.8-ish to 4.1.0-5. And as this wasn't expected (I should have read and studied more -- it's definitely my fault), a few things have confused me as I've started reading the Puppetlabs site for 4.1 documentation:
>
> 1. It says that config files are now under /etc/puppetlabs/puppet, but the RPM says it installed everything to /etc/puppet as always. Which is right?

The PuppetLabs website refers to PL packages.
Maybe Fedora Packages still have everything in /etc/puppet.

>
> 2. My hiera config, or at least the default .yaml file I set up, isn't being seen -- I suspect this is related to #1, but could something else be to blame? The specific error when running a Puppet 4.1 client against my system (actually, the agent running on the server since this was the first F22 upgrade we did) is:
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evalutaiton Error: Error while evaluating a Function Call, Could not find data item proxy in any Hiera data file and no default supplied at /path/to/manifests/site.pp:25:10 on node puppetserver.foo.net
>
> 3. Has Puppetlabs stopped providing RPMs at their yum server? I haven't seen a full set since F20.

The last set of Packages has been made for Fedora 21:
https://docs.puppetlabs.com/puppet/latest/reference/system_requirements.html#fedora

>
> Thanks,
>
>
> Bret Wortman
>
>
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0e9e133a-1d48-45c3-9a1f-ead296205868%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[jcbollinger]

On Thursday, October 8, 2015 at 11:08:35 AM UTC-5, Bret Wortman wrote:

So I upgraded our Puppet server to Fedora 22, which brought with it an upgrade from Puppet 3.8-ish to 4.1.0-5. And as this wasn't expected (I should have read and studied more -- it's definitely my fault), a few things have confused me as I've started reading the Puppetlabs site for 4.1 documentation:

1. It says that config files are now under /etc/puppetlabs/puppet, but the RPM says it installed everything to /etc/puppet as always. Which is right?

The PL docs describe the *default* location for the config directory.  Puppet supports the config directory being located elsewhere, instead, and apparently the Fedora RPMs take advantage of that to continue to use the same location that older Puppet uses.

 

2. My hiera config, or at least the default .yaml file I set up, isn't being seen -- I suspect this is related to #1, but could something else be to blame? The specific error when running a Puppet 4.1 client against my system (actually, the agent running on the server since this was the first F22 upgrade we did) is:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evalutaiton Error: Error while evaluating a Function Call, Could not find data item proxy in any Hiera data file and no default supplied at /path/to/manifests/site.pp:25:10 on node puppetserver.foo.net

I can't explain that one based on the information provided.  Possibly the master's logs will contain more information.

You write in your other message that you saw that environments changed in Puppet 4, but that's not entirely true.  Puppet 4 removes config-file environments, leaving directory environments as the only implementation.  Puppet 3 had directory environments from version 3.6, however, and the data directory path you specified suggests that you may be using them already.  There might still be a configuration issue in this area, however, related to the change in default file locations.

 

3. Has Puppetlabs stopped providing RPMs at their yum server? I haven't seen a full set since F20.

Puppet switched to all-in-one packages, with different package names.  They do provide these via their YUM repos.  When last I checked, Fedora persisted with per-component packaging, which I strongly prefer.  It looks like Fedora is slightly behind, since Puppet 4.2 is the most current, but PL revs versions pretty fast.  For me, avoiding AIO packaging is reason enough to use Fedora's RPMs over PL's, but I also am generally biased toward the OS-provider's packages.

John