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

--detailed-exitcodes not honoured for errors with "puppet agent"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: PUP 3.6.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Linux x86_64
      Ruby 1.9.3p545 (a rebuild of a fedora package running on CentOS 6)
      Puppet 3.6.2 client and server

    • Template:

      Description

      When "puppet agent --detailed-exitcodes" encounters an error, it exits with status 1. The docs suggest that should be either a 4 or a 6, depending on whether changes also occurred.

      Example:

      [root@server tmp]# /usr/bin/puppet agent -v --detailed-exitcodes --ignorecache --no-usecacheonfailure --no-daemonize --onetime --server puppetmaster --environment=dev --waitforcert 60
      Info: Retrieving pluginfacts
      Info: Retrieving plugin
      Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find template 'puppet/run-puppet.tpl' at /puppet/environments/dev/modules/puppet/manifests/init.pp:15 on node puppetmaster
      Warning: Not using cache on failed catalog
      Error: Could not retrieve catalog; skipping run
      [root@server tmp]# echo $?
      1
      [root@server tmp]#

      Note, this also seems to affect "puppet apply".

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            simkin Alan Hodgson
            QA Contact:
            Erik Dasher
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support