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

Exceptions during transaction evaluate reported as success

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PUP 4.10.0, PUP 5.3.3
    • Fix Version/s: PUP 4.10.10, PUP 5.3.4, PUP 5.4.0
    • Component/s: None
    • Labels:
      None
    • Template:
      PUP Bug Template
    • Acceptance Criteria:
      Hide

      When there is an uncaught exception in transaction.evaluate, at a minimum overall status should be 'failed'.

      Show
      When there is an uncaught exception in transaction.evaluate, at a minimum overall status should be 'failed'.
    • Sub-team:
    • Team:
      Platform Core
    • Sprint:
      Platform Core KANBAN
    • Method Found:
      Other (please specify in description)
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Before this change, exceptions in prefetch were not marked as failed in the report. After this change, only transactions that finish processing are marked as successful.
    • QA Risk Assessment:
      No Action

      Description

      Forked off of PUP-7630, to handle only the issue that overall success is reported when an exception is not caught inside transaction.evaluate.

      Actually affects versions as far back as pup 4.0.0-rc1.

        Attachments

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. PUP-8342 Add transaction_completed to schema

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. PUP-7630 "Successful" puppet agent reports hide provider errors

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              eric.delaney Eric Delaney
              Reporter:
              kris.bosland Kris Bosland
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support