CREAM should be able to immediately kill also queued jobs, when the proxy is expiring

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • 1.16.1, 1.14.5
    • Affects Version/s: None
    • Security Level: Public (Visbile by non-authn users.)
    • None

      GGUS: https://ggus.eu/tech/ticket_show.php?ticket=92758
      Savannah: https://savannah.cern.ch/bugs/?86700
      Savannah: https://savannah.cern.ch/bugs/?71100

      CREAM running jobs whose proxy is expiring are killed. If a job is instead queued and its proxy expired, such killing is done only when the CREAM jw starts. CREAM instead should be able to kill such queued jobs as soon as the proxy expired. This is not a problem for jobs submitted through the WMS, since such killing is triggered by the WMS.
      Approach for solving this issue: whenever a delegation proxy expires, all related jobs will be cancelled by CREAM. This simplify the logic and free the queue from jobs which have no way to be executed properly due to the expired proxy.

        1. reg_test_issue_CREAM-83.txt
          4 kB

            Assignee:
            Lisa Zangrando
            Reporter:
            Lisa Zangrando
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: