Ask Your Question

Revision history [back]

The filebucket viewer documentation says that you need the following code in your site.pp file:

filebucket { "main":
  server => "{your puppet master}",
  path => false,
}

File { backup => "main" }

Have you placed that code there yet? If not, please do that and retry the scenario.

The filebucket viewer documentation says that you need the following code in your site.pp file:

filebucket { "main":
  server => "{your puppet master}",
  path => false,
}

File { backup => "main" }

Have you placed that code there yet? If not, please do that and retry the scenario.

After further research, it appears that Puppet Dashboard is working as designed - only the old version of the file is linked, and the new one is not. For an explanation, please see this bug report, particularly this part:

The problem is that when Puppet modifies a file, it drops the old version of the file in the Filebucket. It does not drop the new version. This means that the latest log message reflecting a change will never be able to fetch a diff from the REST API – the new file it should be diffing against doesn’t exist in the bucket.

This filebucket behavior prevents a link to the new version of the file and a diff between the old and new. The file /app/views/reports/_resource_statuses.html.haml specifically prevents the new file from having a popup link (e.g. "exclude_md5s" below):

            ...
            ...
            - status.events.each do |event|                  
              %tr{:class => "status #{event.status}"}
                %td= h event.property
                %td= popup_md5s(h(event.message), :exclude_md5s => [event.desired_value])
      %br
            ...