Really long puppet runs...

[llowder]

I've got a 3.0.0 node on Ubuntu 12.04 talking to a 2.7.19 master on Ubuntu 10.04.  Until yesterday, this worked fine (and the other 3.0.0 node works fine as well)

This node is in my 'test' environment and the other node uses  an almost identical node def except is in the 'prod' environment.

I don't know exactly what changed, but I am hoping someone can help me track this down.

Of the two nodes, I did move the one that is still functioning normally out of test and into prod, but other than hostnames and environments, they use the same code base and settings.

I've posted a partial log (sudo puppet agent -t --debug) from the node having problems at https://gist.github.com/4001797

But the basic issue is that puppet runs have started taking 15-20 minutes, and in each case, the long pause is after

Debug: /Schedule[puppet]: Skipping device resources because running on a host
Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson
Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson

is displayed.

I commented out a section of the node def to simplify, and same issues.

Any help in tracking this down would be much appreciated.

[llowder]

Turns out it was a stray recurse => true

[Paul Tötterman]

I've got a 3.0.0 node on Ubuntu 12.04 talking to a 2.7.19 master on Ubuntu 10.04.

Stop. That is not supported. Master must be newer or equal to client. 

[Nikola Petrov]

Is there any particular reason that you are using an older master than
the client. If not now it will pop up as a problem in the future. Why
don't you just make the move?

Best, Nikola

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WtV8zCBVI1YJ.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>

[llowder]

On Friday, November 2, 2012 1:10:37 PM UTC-5, nikolavp wrote:

Is there any particular reason that you are using an older master than
the client. If not now it will pop up as a problem in the future. Why
don't you just make the move?

2 of my nodes got provisioned wrong. I am ready to upgrade my master and the rest of my nodes, but corporate policy will not allow me to at this point in time.

As it currently stands, 3.0.0 client talking to a 2.7.19 master is relatively safe. The issue I was having was unrelated to the versions being used.

I am well aware of the potential problems when a client is newer than a master, and I do not plan on running this way any longer than I have to.