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

Collapse dependency failures into Class level failures

    XMLWordPrintable

    Details

    • Template:
    • Team:
      Night's Watch
    • Story Points:
      3
    • Sprint:
      NW - 2019-10-02, NW - 2019-10-16, NW - 2019-10-30, NW - 2019-11-13, 2019-11-27
    • CS Priority:
      Reviewed
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      Merge dependency warnings

      If a class has a failed dependency, every individual resource in that class generates a `notice` level message about the dependency failure, and a `warning` level message about skipping the resource. At large-node and/or large-code scale, one dependency failure can create an overwhelming number of warnings ... obscuring the root cause and increasing the use of system resources required to process and store the resulting reports.

      To collapse all messages caused by one class dependency failure into one message associated with the class, set `merge_dependency_warnings=true`.
      Show
      Merge dependency warnings If a class has a failed dependency, every individual resource in that class generates a `notice` level message about the dependency failure, and a `warning` level message about skipping the resource. At large-node and/or large-code scale, one dependency failure can create an overwhelming number of warnings ... obscuring the root cause and increasing the use of system resources required to process and store the resulting reports. To collapse all messages caused by one class dependency failure into one message associated with the class, set `merge_dependency_warnings=true`.
    • QA Risk Assessment:
      Needs Assessment

      Description

      When a Class has a failed dependency, every individual resource in the class generates a notice level message about the dependency failure and a warning level message about skipping the resource, as well as a skip event in the report. This can generate a large number of messages and a large report if there are many dependencies, or multiple layers of dependencies.

      At large-node and/or large-code scale, one dependency failure can create an overwhelming number of warnings ... obscuring the root cause and increasing the use of system resources required to process and store the resulting reports.

      If possible, all of the skipped resources should be collapsed into the containing class and the messages and skip event should be done at the class level. It looks like the most recent work on this was done in PUP-3930 and commit 32e2bf2.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dorin.pleava Dorin Pleava
              Reporter:
              adrian.parreiras-horta Adrian Parreiras Horta
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support