Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-3360

Clients do not report failures to puppetdb when the puppetmaster no longer gives them a valid catalog

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 3.6.2
    • Fix Version/s: None
    • Component/s: Catalog Application
    • Labels:
      None
    • Environment:

      Puppet 3.6.2 RPMs from Puppet Labs

    • Template:

      Description

      After deploying Directory Environments, we are seeing errors in catalog compilation on a few hosts (I have filed a separate bug about this). The problem here is that this error not logged anywhere except syslog, and therefore we didn't detect the problem for several hours after the fact. This is a problem.

      The sample syslog run:

      Sep 29 09:50:12 cmsstordb2 puppet-agent[869]: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class s_nfs at /srv/puppet/environments/squidplus/modules/role/manifests/server/nfs.pp:16 on node cmsstordb2.fnal.gov
      Sep 29 09:50:13 cmsstordb2 puppet-agent[869]: Using cached catalog
      Sep 29 09:50:31 cmsstordb2 puppet-agent[869]: Finished catalog run in 17.58 seconds

      This successfully sent a report up to the puppetdb, which indicates that there were no events and no errors.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kylo Kylo Ginsberg
              Reporter:
              tskirvin Tim Skirvin
              QA Contact:
              Eric Thompson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support