uploading manifests/classes to puppet enterprise - when trying to install "agents curl: (7) couldn't connect to host"

asked 2015-04-13 14:14:04 -0500

davebenham gravatar image

Not exactly sure about the best workflow to use in development of my custom classes.

When I upload custom classes onto my PE master and they contain the smallest syntax error, when I attempt to connect to the PE master from an PE agent, I just get a generic "curl: (7) couldn't connect to host" error.

When I dig through the logs on my PE master, I find references to parse errors, as would be expected, but I'm not sure how to test my puppet code without loading it onto the server and distributing it to an agent and see what happens.

Is there an environment I can pretest my puppet classes in before uploading them to my PE master? I started testing code on a standalone puppet server, but I can't run the same exact code on the standalone install as I would in the PE master, so I still have problems.

It would help if the response from a puppet master encountering a parse error in one of it's classes would return something more helpful than 'cannot connect to host' error to any agents phoning home, but I can accept this behaviour.

I need to know the proper way to test a class before putting it on a PE master server.

Sorry in advance if this is the wrong forum, or I am not clear in my issue.

Thanks Dave Benham

edit retag flag offensive close merge delete


You can use "puppet parser validate" to check syntax locally and "puppet apply" to test locally before uploading to a Puppet master. Can you post a link to a pastebin of output that contains the curl error message? I haven't seen that caused by a parse error, so I'm interested to see more.

GregLarkin gravatar imageGregLarkin ( 2015-04-13 23:46:10 -0500 )edit