Project

General

Profile

Bug #295

This YAML generates a 500 error when trying to send over http.

Added by Bash Shell almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Importers
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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.

Associated revisions

Revision 895a7680 (diff)
Added by Ohad Levy almost 9 years ago

fixes #295 - This YAML generates a 500 error when trying to send over http

History

#1 Updated by Bash Shell almost 9 years ago

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?

#2 Updated by Ohad Levy almost 9 years ago

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

#3 Updated by Ohad Levy almost 9 years ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100

#4 Updated by Ohad Levy almost 9 years ago

  • Category set to Importers
  • Assignee set to Ohad Levy
  • Target version set to 0.1-5

#5 Updated by Bash Shell almost 9 years ago

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 .

#6 Updated by Ohad Levy almost 9 years ago

  • Status changed from Ready For Testing to Closed

would you mind adding your experiences to the troubleshooting section?

Also available in: Atom PDF