Puppet

Can we get a stack trace?

If you tell me how, sure… running with —trace —debug only shows this:

debug: //baseclass/redhat/redhat::crashdump/Notify[No crashdump setup for RHEL5 yet]: Changing message debug: //baseclass/redhat/redhat::crashdump/Notify[No crashdump setup for RHEL5 yet]: 1 change(s) notice: No crashdump setup for RHEL5 yet notice: //baseclass/redhat/redhat::crashdump/Notify[No crashdump setup for RHEL5 yet]/message: defined ‘message’ as ‘No crashdump setup for RHEL5 yet’ debug: Finishing transaction -615421398 with 5 changes debug: Storing state debug: Stored state in 0.32 seconds err: Reporting failed: Server returned 400: undefined method `save' for false:FalseClass notice: Finished catalog run in 27.43 seconds

Looks like we need the server-side trace. Can you paste that?

I filed a similar issue on 2367, I keep forgetting to post the trace, I should get to it tonight… Is this also an apache-> mongrel setup I wonder?

Yes apache->mongrel. :) This bug is very likely a dupe of 2367.

We tried to run a debug server with this command:

puppetmasterd —no-daemonize —servertype webrick —storeconfigs false —masterport 9844 —debug —trace 2>&1 | tee /tmp/lakwtf

But it wasn’t very trace-y and the debug info didn’t seem interesting. I’m happy to paste it though if you want.

We didn’t get the save error (this bug) but we did get the to_sym error on the client. Nothing in the server log though when it happened.

I’m changing the “affected version” because this is a 25b2->25b2 problem.

As Sam says, I think this is a dupe, it’s reporting failing.