Bug #11268
closed
foreman discover client boot up fine but unable to send fact
Description
this is a foreman server was previously working. all over sudden, it stopped working and give fact cache invalid message when the discovered client boot up and not able to register the message to foreman. it get 500 response from foreman. see screenshot and foreman-debug in the attachment.
thanks,
Files
| screenshot.jpg | View screenshot.jpg | 93.1 KB | |||
| foreman-debug-H3shk.tar.xz | foreman-debug-H3shk.tar.xz | 32 Bytes |
Updated by Dominic Cleal about 9 years ago
- Project changed from Foreman to Discovery
This looks like bug #9857.
Updated by tony zheng about 9 years ago
interesting... this same client was working before through... i merely deleted it and trying to re-discover again.
Updated by Lukas Zapletal about 9 years ago
- Status changed from New to Need more information
Please note a workaround, set 'ignore_puppet_facts_for_provisioning' setting to false (Administer -> Settings).
Close the bug if this fixes the problem. Thanks!
Updated by Lukas Zapletal about 9 years ago
Off topic: We'd appreciate putting your company on http://projects.theforeman.org/projects/1/wiki/Who_Uses_Foreman if that's possible. Thanks. :-)
Updated by tony zheng about 9 years ago
yes that did worked.
Cool!
yes you can but just so you know we are still in the experiment stage of foreman, once everything working then we will make it production. let's make that happen ;)
Updated by Tomer Brisker over 8 years ago
- Status changed from Need more information to Resolved
Seems to have been resolved. Closing.