foreman_proxy registration issue with 2.5.0 and foreman 1.11.1

Question

foreman_proxy registration issue with 2.5.0 and foreman 1.11.1

mleklund opened this issue 8 years ago · comments

I don't have much to go on other then log entries that look like this:

Apr 27 10:32:08 cfg01 puppet-agent[15348]: (/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[cfg01.phx.dealnews.net]) Could not evaluate: Proxy cfg01.phx.dealnews.net cannot be registered ("\xE2" on US-ASCII): N/A

Dominic Cleal · Answer 1 · Wed Apr 27 2016 23:00:28 GMT+0800 (China Standard Time)

Any logs from the (Foreman) server? Debug logs from the agent?

Michael Eklund · Answer 2 · Wed Apr 27 2016 23:59:05 GMT+0800 (China Standard Time)

grrr... I can't make it happen on foreground runs, but happens repeatedly on background runs. There does not seem to be anything in the foreman server logs. I will keep digging.

Dominic Cleal · Answer 3 · Thu Apr 28 2016 00:47:34 GMT+0800 (China Standard Time)

The error message and that fact suggest it might be the agent is running in a non-Unicode locale, which is the default on certain versions of Ruby. Perhaps it's struggling to read the API metadata or response when that happens.

Commenting the rescue/exception handler code in the provider (in the foreman module) to get a full message and stack trace, plus debug information from the agent may provide more context.

Michael Eklund · Answer 4 · Thu Apr 28 2016 23:08:52 GMT+0800 (China Standard Time)

I wiped out my puppet state directory and the problem went away, so something in the puppet agent state was forcing ASCII instead of utf-8.