trunk's pegasus-run fails to start a workflow

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical
    • master, 4.0.1
    • Affects Version/s: master
    • Component/s: CLI: pegasus-run
    • None

      When I execute the pegasus-run on synthale to start a workflow, it goes through all the motions of starting it (and reporting success). However, it does not start anything, i.e. the Condor Q is empty afterwards :-O

      /voeckler/pegasus/page-clean/run0020

      -----------------------------------------------------------------------
      File for submitting this DAG to Condor : page-clean-0.dag.condor.sub
      Log of DAGMan debugging messages : page-clean-0.dag.dagman.out
      Log of Condor library output : page-clean-0.dag.lib.out
      Log of Condor library error messages : page-clean-0.dag.lib.err
      Log of the life of condor_dagman itself : page-clean-0.dag.dagman.log

      Submitting job(s).
      1 job(s) submitted to cluster 462.
      -----------------------------------------------------------------------

      Your Workflow has been started and runs in base directory given below

      cd /home/voeckler/page/upload/submit/voeckler/pegasus/page-clean/run0020

          • To monitor the workflow you can run ***

      pegasus-status -l /home/voeckler/page/upload/submit/voeckler/pegasus/page-clean/run0020

          • To remove your workflow run ***
            pegasus-remove /home/voeckler/page/upload/submit/voeckler/pegasus/page-clean/run0020

      voeckler@synthale:~/page/upload $ echo $?
      0

      voeckler@synthale:~/page/upload $ condor_q

      – Submitter: synthale.isi.edu : <128.9.xxx.xxx:38510> : synthale.isi.edu
      ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD

      0 jobs; 0 idle, 0 running, 0 held

      Did someone change something of significance in trunk? Maybe the Python tools/utils change affected this?

            Assignee:
            Gaurang Mehta (Inactive)
            Reporter:
            Jens Voeckler
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: