Problem upgrading to puppetserver 2.5.0 and exported resources

15 views
Skip to first unread message

Angel L. Mateo

unread,
Sep 7, 2016, 8:19:43 AM9/7/16
to puppet...@googlegroups.com
Hello,

I am upgrading my puppetservers (ubuntu 14.04) from 2.4.0 to 2.5.0.
Upgrading process it's fine, but after it whenever I connect a node
(puppet-agent 1.5.3 or puppet-agent 1.6.2) I'm having a lot of messages
about creating resources that are actually defined as exported for that
node.

I mean I'm having messages like:

Notice:
/Stage[main]/Profile::Nagios/Omd_nagios_service[tlm_sorex12_DISCO
/]/ensure: current_value absent, should be present (noop)
Notice: /Stage[main]/Profile::Nagios/Omd_nagios_service[tlm_sorex12_Load
Average]/ensure: current_value absent, should be present (noop)

but those resources are defined with:

create_resources('@@omd_nagios_service', $nagios_services,...)

(where $nagios_services is a hash read from hiera)

any help?

--
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
http://www.um.es/atica
Tfo: 868889150
Fax: 868888337

Andrew Grimberg

unread,
Sep 7, 2016, 10:59:19 AM9/7/16
to puppet...@googlegroups.com
On 09/07/2016 05:19 AM, Angel L. Mateo wrote:
> Hello,
>
> I am upgrading my puppetservers (ubuntu 14.04) from 2.4.0 to 2.5.0.
> Upgrading process it's fine, but after it whenever I connect a node
> (puppet-agent 1.5.3 or puppet-agent 1.6.2) I'm having a lot of messages
> about creating resources that are actually defined as exported for that
> node.
>
> I mean I'm having messages like:
>
> Notice:
> /Stage[main]/Profile::Nagios/Omd_nagios_service[tlm_sorex12_DISCO
> /]/ensure: current_value absent, should be present (noop)
> Notice: /Stage[main]/Profile::Nagios/Omd_nagios_service[tlm_sorex12_Load
> Average]/ensure: current_value absent, should be present (noop)
>
> but those resources are defined with:
>
> create_resources('@@omd_nagios_service', $nagios_services,...)
>
> (where $nagios_services is a hash read from hiera)
>
> any help?

Greetings Angel,

There's an issue raised [0] about this already. The issue isn't exactly
with the new puppetserver but with the puppet-agent 1.6.0 - 1.6.2 on the
puppet server.

My experience has been that updating client systems to the latest
puppet-agent isn't a problem, only if you've updated the agent on the
puppetserver. Unfortunately puppetserver 2.5.0 requires an agent >=
1.6.0 :-/

-Andy-

[0] https://tickets.puppetlabs.com/browse/SERVER-1495

signature.asc
Reply all
Reply to author
Forward
0 new messages