Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-1121

Store reasons for workflow failure in stampede database

XMLWordPrintable

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major Major
    • master, 4.7.0
    • Affects Version/s: master
    • Component/s: Monitord
    • None

      If a user does a condor rm on a running workflow, the workflow is marked failed in the database but why it failed is not logged. the new "reason" column in workflow state table should be updated both for dashboard databases and workflow database

      Related to JIRA PM-749 and PM-767

            Assignee:
            vahi Karan Vahi
            Reporter:
            mayani Rajiv Mayani
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: