Red Hat Bugzilla – Bug 768319
provide information of suspended jobs
Last modified: 2013-03-06 13:40:24 EST
Description of problem: There is information about suspended jobs in condor_q output but it is not in aviary in list of submissions. $./submissions.py --u=http://_X_:9091/services/query/getSubmissionSummary --name="_X_#159" [(SubmissionSummary){ id = (SubmissionID){ name = "_X_#159" owner = "condor" } status = (Status){ code = "OK" } qdate = 1321867162 completed = 0 held = 0 idle = 0 removed = 0 running = 0 }] $ condor_q 159 -- Submitter: _X_ : <_x_:35875> : _X_ ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD 159.0 condor 11/21 04:19 3+19:40:51 S 0 9.8 wait.bat 1000000 There is now just correct information in getJobStatus output. $ ./jobquery.py --u=http://_X_:9091/services/query/ --cmd=getJobStatus --cproc=159.0 invoking http://_X_:9091/services/query/getJobStatus for job 159.0 [(JobStatus){ id = (JobID){ job = "159.0" pool = "_X_" scheduler = "_X_" } status = (Status){ code = "OK" } job_status = "SUSPENDED" }] Version-Release number of selected component (if applicable): condor-aviary-7.6.5-0.10 How reproducible: 100% Steps to Reproduce: 1. install and setup condor and aviary 2. run command above Actual results: There is no information about suspended jobs in list of submissions. Expected results: There is information about suspended jobs in all possible outputs of aviary.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: Invoke the Aviary query operation getSubmissionSummary on a submission with suspended jobs. Consequence: There are no totals listed for suspended jobs in the summary. Fix: Aviary XSD updated and implementation code added to include submission totals in summary. Result: Submission totals are now listed in submission summary.
Tested on RHEL 5.9/6.4 x x86_64/i386 with condor-7.8.7-0.6.el6_3.x86_64 condor-aviary-7.8.7-0.6.el6_3.x86_64 condor-classads-7.8.7-0.6.el6_3.x86_64 condor-wallaby-base-db-1.25-1.el6_3.noarch condor-wallaby-client-5.0.4-1.el6_3.noarch condor-wallaby-tools-5.0.4-1.el6_3.noarch python-condorutils-1.5-6.el6.noarch python-qpid-0.18-4.el6.noarch python-qpid-qmf-0.18-13.el6.x86_64 python-wallabyclient-5.0.4-1.el6_3.noarch qpid-cpp-client-0.18-13.el6.x86_64 qpid-cpp-server-0.18-13.el6.x86_64 qpid-qmf-0.18-13.el6.x86_64 ruby-condor-wallaby-5.0.4-1.el6_3.noarch ruby-qpid-qmf-0.18-13.el6.x86_64 ruby-wallaby-0.16.1-2.el6.noarch wallaby-0.16.1-2.el6.noarch wallaby-utils-0.16.1-2.el6.noarch and it works. --> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0564.html