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

pegasus is not constructing transfer jobs for http urls correctly

XMLWordPrintable

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major Major
    • None
    • Affects Version/s: 4.7.1
    • Component/s: Pegasus Planner
    • None

      If the URL of an executable is given with a http URI (rather than gsiftp) then pegasus-plan writes a bad shell script as it doesn't create a stage in transfer for the executable.

      Instead, it just passes the URL to kickstart:

      pegasus-kickstart -n inspiral-BNS02_INJ-H1_ID157 -N ID0032000 -R osg -L main -T 2016-11-10T17:51:17-05:00 http://pycbc.phy.syr.edu/pycbc-software/v1.5.5/x86_64/composer_xe_2015.0.090/pycbc_inspiral --pad-data 8 --strain-high-pass 20 --sample-rate 4096 --segment-length 256 ...

      and kickstart fails with

      kickstart[642339]: pegasus-kickstart.c[673]: FATAL: The main job specification is invalid or missing.

      There should be a transfer for the http URL so pegasus-transfer can move it and chmod it correctly before it is run (or kickstart needs to be modified to be able to pull the executable via http itself).

            Assignee:
            vahi Karan Vahi
            Reporter:
            dbrown Duncan Brown
            Watchers:
            2 Start watching this issue

              Created:
              Updated: