Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-12524

Manual schedule execution produces fake run records

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: rel-4-6-1
    • Fix Version/s: rel-4-9-0
    • Component/s: Server
    • Security Level: Users (General product issues)
    • Labels:
    • Story Points:
      1
    • QA Testing:
      UNDECIDED
    • Steps to reproduce:
      Hide

      1) have a two-node cluster

      2) have a graph running over 30 s

      3) define a schedule to the graph above, configure the schedule not to persist the run record
      4) 'Run now' the schedule for several times

      5) for runs delegated to other cluster nodes, run record is persisted in N/A state - the execution history considers such jobs as running and displays 'Kill' actions, but the jobs cannot be killed. Moreover, these run records do not have log files.

      Show
      1) have a two-node cluster 2) have a graph running over 30 s 3) define a schedule to the graph above, configure the schedule not to persist the run record 4) 'Run now' the schedule for several times 5) for runs delegated to other cluster nodes, run record is persisted in N/A state - the execution history considers such jobs as running and displays 'Kill' actions, but the jobs cannot be killed. Moreover, these run records do not have log files.
    • OTRS_Ticket_ID:
      2018010310000137
    • Sprint:
      Green Sprint 61

      Attachments

        Activity

          People

          • Assignee:
            michalicaj Jano Michalica
            Reporter:
            michalicaj Jano Michalica
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: