On Friday, August 17, 2012 9:51:06 AM UTC-4, pmbuko wrote:
>
> Greetings,
>
> I'm testing Fedora 17 in our environment and have come across an
> interesting/annoying issue (that may or may not be isolated to my
> environment). Puppet runs fine on the test node but the reports are failing
> to import to dashboard and are showing up as background task failures with
> these details:
>
>
> Importing report report-19732-119.yaml at 2012-08-17 09:01 EDT
> undefined method `each' for nil:NilClass
>
> Backtrace:
> /opt/puppet-dashboard/lib/puppet/report.rb:202:in `extended'
> /opt/puppet-dashboard/lib/puppet/report.rb:200:in `each'
> /opt/puppet-dashboard/lib/puppet/report.rb:200:in `extended'
> /opt/puppet-dashboard/lib/puppet/report.rb:114:in `extend'
> /opt/puppet-dashboard/lib/puppet/report.rb:114:in `extended'
> /opt/puppet-dashboard/app/models/report.rb:107:in `extend'
> /opt/puppet-dashboard/app/models/report.rb:107:in `create_from_yaml'
> /opt/puppet-dashboard/app/models/report.rb:86:in `create_from_yaml_file'
>
>
> Anyone have any ideas why this might be occurring?
>
> The Fedora 17 node and the puppetmaster are running puppet 2.7.18.
> My puppetmaster has ruby enterprise 1.8.7 (patch level 334), the node
> has ruby 1.9.3p194.
> Puppetmaster is hosting puppet-dashboard version 1.2.10. OS is Scientific
> Linux 5.5.
>
I have a bit more data to add. In looking at the yaml files sent to my
puppetmaster from the Fedora 17 host, I see that the resource statuses are
coming in empty. For example, see this exerpt:
file: 201208201315.yaml
----------
puppet_version: 2.7.18
report_format: 2
resource_statuses:
"Service[cups]": !ruby/object:Puppet::Resource::Status {}
"File[/etc/cups/cupsd.conf]": !ruby/object:Puppet::Resource::Status {}
Note the empty curly brackets.
On a node that's working properly (Fedora 16), I see the following:
file: 201208201333.yaml
----------
puppet_version: 2.7.18
report_format: 2
resource_statuses:
"File[/etc/cups/cupsd.conf]": !ruby/object:Puppet::Resource::Status
change_count: 0
changed: false
evaluation_time: 0.016504
events: []
failed: false
file: *id003
line: 15
out_of_sync: false
out_of_sync_count: 0
resource: "File[/etc/cups/cupsd.conf]"
resource_type: File
skipped: false
tags:
- file
- class
- cups
- node
- janelia.priv
time: 2012-08-20 09:33:49.215995 -04:00
title: /etc/cups/cupsd.conf
"Service[cups]": !ruby/object:Puppet::Resource::Status
change_count: 0
changed: false
evaluation_time: 0.092452
events: []
failed: false
file: &id003 /etc/puppet/modules/cups/manifests/init.pp
line: 22
out_of_sync: false
out_of_sync_count: 0
resource: "Service[cups]"
resource_type: Service
skipped: false
tags:
- service
- cups
- class
- node
- janelia.priv
time: 2012-08-20 09:33:49.233521 -04:00
title: cups
Also, note that I've verified that puppet has correctly applied the cups
resources on the Fedora 17 node.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/2PgqtNlHpbUJ.
To post to this group, send email to puppet-users@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.
