Bug #295
closed
This YAML generates a 500 error when trying to send over http.
Added by Bash Shell almost 14 years ago.
Updated almost 14 years ago.
Description
File is attached.
/usr/local/foredevJun1/extras/puppet/foreman/files/push_facts.rb:34: Could not send facts to Foreman: wrong Content-Length format (RuntimeError)
from /usr/local/foredevJun1/extras/puppet/foreman/files/push_facts.rb:26:in `each'
from /usr/local/foredevJun1/extras/puppet/foreman/files/push_facts.rb:26
The rake task seems to import this OK.
Files
I think this is because the Host and or facts for it exist already and are un-changed?
If so, then a 500 error is not the best indication?
Bash Shell wrote:
I think this is because the Host and or facts for it exist already and are un-changed?
If so, then a 500 error is not the best indication?
that should not be the case, 500 should indicate a problem saving the facts, I'll investigate
- Status changed from New to Ready For Testing
- % Done changed from 0 to 100
- Category set to Importers
- Assignee set to Ohad Levy
- Target version set to 0.1-5
This was because of an out dated mongrel gem.
I though of this when I got a similar error from the external nodes script.
I just ran gem update on this machine.
Sorry for the ticket...
I guess we can have something in the FAQ about checking mongrel/other gems which might affect http .
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by 
Updated by