Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-39247

A job isn't aware its subtask is cancelled, showing incorrect counts

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 6.18.0
    • Tasks Plugin
    • None
    • False
    • sat-endeavour
    • None
    • None
    • None
    • None
    • No

      Description of problem:

      When I cancel a subtask of a job, the job doesn't know and doesn't show it as cancelled.

      How reproducible:

      Deterministic

      Is this issue a regression from an earlier version:

      Reproduced in Sat 6.18 snap 6.0. This happens in the new REX UI. In legacy UI, it wasn't possible to cancel a subtask.

      Steps to Reproduce:

      1. Have a Satellite  with 4 hosts registered

      2. In Hosts, select hosts and "Schedule a job"

      3. On the second tab, set script to `echo $(date) > /tmp/test; sleep 60; echo done >> /tmp/test;`

      4. On the third tab, set concurrency to 2

      5. Submit

      6. Select all the subtasks and in the kebab menu, "Cancel selected"

      7. Go to Monitor -> Satellite Tasks -> Tasks

      8. Click the parent task and then Dynflow Console

      9. On the Run tab, select the RunHostsJob task

      Actual behavior

      Output:

      ---
      host_count: 4
      remote_triggered_count: 4
      planned_count: 4
      cancelled_count: 0
      total_count: 4
      failed_count: 2
      pending_count: 0
      success_count: 2 

      Expected behavior:
      The tasks should be reported as cancelled

              Unassigned Unassigned
              lhellebr@redhat.com Lukas Hellebrandt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: