Debugging Puppet catalog compilation issues

208 views
Skip to first unread message

Frederic Conrotte

unread,
Mar 24, 2015, 8:10:25 AM3/24/15
to puppet...@googlegroups.com
Hello

I'm using Puppet Master 3.7 thru Apache/Passenger and I am facing this compilation issue:

[1;31mError: Could not retrieve catalog from remote server: Error 400 on SERVER: assert_type(): Expected type String[1, default] does not match actual: Float on node (...)[0m

I have been looking in Puppet Master logs to find the root cause but found nothing useful so far.

Can you explain why catalog compilation failures do not give either the class name or the .pp file where the issue occurs ?

It would make developers life much easier.

Nick Howes

unread,
Mar 24, 2015, 9:47:13 AM3/24/15
to puppet...@googlegroups.com


On Tuesday, 24 March 2015 12:10:25 UTC, Frederic Conrotte wrote:
Hello

I'm using Puppet Master 3.7 thru Apache/Passenger and I am facing this compilation issue:

[1;31mError: Could not retrieve catalog from remote server: Error 400 on SERVER: assert_type(): Expected type String[1, default] does not match actual: Float on node (...)[0m


I raised this bug (where most function exceptions wouldn't include any file/line info) a few weeks ago, and a fix has been made to Puppet, which should appear in 3.7.5.

Here it is

Frederic Conrotte

unread,
Mar 25, 2015, 2:46:48 AM3/25/15
to puppet...@googlegroups.com
Thanks for your answer Nick, I will surely try this when 3.7.5 is out
Reply all
Reply to author
Forward
0 new messages