Hello Fellows,
 I am running into an odd bug trying to setup External Nodes with
Puppet Dashboard. I have a presentation to give to my clients by
12:00PM. I was hoping to show them how to manage classes and nodes
using the DB. Many thanks if the solution jumps out at anyone and they
can help me before the meeting.

 Well anyways the problem is as folllows:
  Running the /usr/local/puppet-dashboard/bin/external_node script
with out a hostname produces the following:
[r...@config bin]# ./external_node
---
  - !ruby/object:Node
    attributes:
      name: sample_node
      updated_at: 2010-06-15 14:38:02
      url:
      id: "1"
      description:
      reported_at: 2009-11-20 01:08:50
      created_at: 2010-06-15 14:38:02
    attributes_cache: {}
  - !ruby/object:Node
    attributes:
      name: test-vm.***********.com
      updated_at: 2010-06-24 15:11:31
      url:
      id: "2"
      description: Tom's Test VM for his Puppet Work
      reported_at: 2010-06-24 15:11:30
      created_at: 2010-06-15 14:47:36
    attributes_cache: {}

Running it with a hostname produces the following:
[r...@config bin]# ./external_node test-vm.*******.com
Error: 500 Internal Server Error

The pupet-dashboard log shows the following:
ArgumentError (wrong number of arguments (1 for 0)):
  app/models/node.rb:69:in `to_yaml'
  app/models/node.rb:69:in `to_yaml'
  haml (2.2.2) [v] rails/./lib/sass/plugin/rails.rb:19:in `process'
  /usr/lib/ruby/1.8/thread.rb:135:in `synchronize'
  /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
  /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
  /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
  /usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
  /usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
  /usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
  /usr/lib/ruby/1.8/webrick/server.rb:82:in `start'


I found the following resource stating that a solution was to add the
.inspect or .name to the node.rb to_yaml method, neither helped. Any
help with this would be greatly appreciated.

 Have a great day everyone!

-Tom

Thomas A. McGonagle
t...@dataero.com
Google Voice: 617-229-5185

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to