Clustered jobs in workflows using condor file transfers get -w kickstart option when they should not

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • 2.4.3, master, 3.0
    • Affects Version/s: master
    • Component/s: Pegasus Planner
    • None

      When I use condor file transfers and cluster the workflow using label-based clustering Pegasus generates the -w working directory option and sets it to a generated path in /tmp. This breaks the workflow because condor transfers all the input files to the condor exec directory. This problem does not get triggered if the workflow is not clustered.

            Assignee:
            Karan Vahi
            Reporter:
            Gideon Juve (Inactive)
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: