puppet stop working

62 views
Skip to first unread message

Albert Shih

unread,
Feb 2, 2017, 8:28:30 AM2/2/17
to puppet...@googlegroups.com
Hi,

We just update puppet-agent (Debian, puppetlabs repot) on the puppetserver
(last version), and every agent stop working with this error


Info: Using configured environment 'jas'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: hiera configuration version 3 cannot be used in an environment on node node_fqdn
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run


Anyone have this problem ?

Any idea ?

Regards

JAS
--
Albert SHIH
DIO bātiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
xmpp: j...@obspm.fr
Heure local/Local time:
jeu 2 fév 2017 14:26:45 CET

Albert Shih

unread,
Feb 2, 2017, 9:33:07 AM2/2/17
to puppet...@googlegroups.com
Le 02/02/2017 à 14:28:17+0100, Albert Shih a écrit
> Hi,
>
> We just update puppet-agent (Debian, puppetlabs repot) on the puppetserver
> (last version), and every agent stop working with this error
>
>
> Info: Using configured environment 'jas'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: hiera configuration version 3 cannot be used in an environment on node node_fqdn
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
>
> Anyone have this problem ?

It's seem it's because the apt-get upgrade install the new-futur version of
puppet-agent 1.9.0 and come with new hiera module.

So don't upgrade you puppet-agent until official annoncement (something I
always shoud do...)

>
> Any idea ?

To solve the problem go back with the previous version (1.8.x) restart the
puppetserver.

Regards.
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
xmpp: j...@obspm.fr
Heure local/Local time:
jeu 2 fév 2017 15:31:15 CET

Henrik Lindberg

unread,
Feb 2, 2017, 12:10:25 PM2/2/17
to puppet...@googlegroups.com
On 02/02/17 14:28, Albert Shih wrote:
> Hi,
>
> We just update puppet-agent (Debian, puppetlabs repot) on the puppetserver
> (last version), and every agent stop working with this error
>
>
> Info: Using configured environment 'jas'
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: hiera configuration version 3 cannot be used in an environment on node node_fqdn
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
>
> Anyone have this problem ?
>
> Any idea ?
>

You have a hiera.yaml in the root of your environment. It should not be
there. Rename it or move it out of the way.

Best,
- henrik



--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

Albert Shih

unread,
Feb 3, 2017, 8:00:05 AM2/3/17
to puppet...@googlegroups.com
Le 02/02/2017 à 18:09:58+0100, Henrik Lindberg a écrit
> On 02/02/17 14:28, Albert Shih wrote:
> > Hi,
> >
> > We just update puppet-agent (Debian, puppetlabs repot) on the puppetserver
> > (last version), and every agent stop working with this error
> >
> >
> > Info: Using configured environment 'jas'
> > Info: Retrieving pluginfacts
> > Info: Retrieving plugin
> > Info: Loading facts
> > Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: hiera configuration version 3 cannot be used in an environment on node node_fqdn
> > Warning: Not using cache on failed catalog
> > Error: Could not retrieve catalog; skipping run
> >
> >
> > Anyone have this problem ?
> >
> > Any idea ?
> >
>
> You have a hiera.yaml in the root of your environment. It should not be
> there. Rename it or move it out of the way.

You're absolute right.

Here the thing you NEED to do when you pass to 1.9.0 :

Make sure you don't have ANY hiera.yaml in /code/environments/*

Make sure you don't have any EMPTY hiera file in hieradata

after that everything work fine.

Regards.

JAS
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
xmpp: j...@obspm.fr
Heure local/Local time:
ven. 3 févr. 2017 13:58:35 CET
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: j...@obspm.fr
Heure local/Local time:
ven. 3 févr. 2017 13:59:50 CET

Henrik Lindberg

unread,
Feb 3, 2017, 8:04:28 AM2/3/17
to puppet...@googlegroups.com
On 03/02/17 13:59, Albert Shih wrote:
> Le 02/02/2017 à 18:09:58+0100, Henrik Lindberg a écrit
>> On 02/02/17 14:28, Albert Shih wrote:
>>> Hi,
>>>
>>> We just update puppet-agent (Debian, puppetlabs repot) on the puppetserver
>>> (last version), and every agent stop working with this error
>>>
>>>
>>> Info: Using configured environment 'jas'
>>> Info: Retrieving pluginfacts
>>> Info: Retrieving plugin
>>> Info: Loading facts
>>> Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: hiera configuration version 3 cannot be used in an environment on node node_fqdn
>>> Warning: Not using cache on failed catalog
>>> Error: Could not retrieve catalog; skipping run
>>>
>>>
>>> Anyone have this problem ?
>>>
>>> Any idea ?
>>>
>>
>> You have a hiera.yaml in the root of your environment. It should not be
>> there. Rename it or move it out of the way.
>
> You're absolute right.
>
> Here the thing you NEED to do when you pass to 1.9.0 :
>
> Make sure you don't have ANY hiera.yaml in /code/environments/*
>
> Make sure you don't have any EMPTY hiera file in hieradata
>
> after that everything work fine.
>
> Regards.
>
> JAS

Thanks JAS for the writeup. Both of these problems will be addressed in
a 4.9.2 release coming shortly.

In 4.9.2 you should still move the hiera.yaml out of environment roots,
but it will not fail if there is a hiera.yaml version 3 file there.

Best, and sorry for all the trouble.
Reply all
Reply to author
Forward
0 new messages