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

pegasus-python-wrapper locates executable from PEGASUS_HOME instead of dirname of the exec.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: master, 5.0.0
    • Component/s: CLI: pegasus-transfer
    • Labels:
      None

      Description

      shared-fs mode
      worker staging true
      PEGASUS_HOME set on shared-fs site

      The create-dir job's sub file has the correct pegasus-transfer, but when it is intercepted by pegasus-python-wrapper, it ends up using the pegasus-transfer from PEGASUS_HOME set on remote site.

      sub-file: executable = /lfs1/software/bamboo/data/xml-data/build-dir/PEGASUS-WT50-T10D/pegasus/bin/pegasus-transfer
      p-transfer being located by py-wrapper - /lizard/scratch-90-days/bamboo/scratch/20200328_012026983672830/bamboo/pegasus/horizontal-clustering-test/20200328T012028-0700/pegasus-5.0.0dev/lib64/python3.6/site-packages/Pegasus/cli/pegasus-transfer.py

      https://bamboo.isi.edu/browse/PEGASUS-WT50-T10D-432/log
      See: 00/00/create_dir_horizontal-clustering-test_0_sharedfs.sub
      See: catalogs/sites.xml

      The wrapper should mimic p-config and locate executable based on the dirname of the tool being invoked.

        Attachments

          Activity

            People

            • Assignee:
              rynge Mats Rynge
              Reporter:
              mayani Rajiv Mayani
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: