Description of problem: There are these states (ns0:JobStatusType){ IDLE = "IDLE" RUNNING = "RUNNING" REMOVED = "REMOVED" COMPLETED = "COMPLETED" HELD = "HELD" } in SOAP type ns0:JobStatusType. There should be all states of job so also "Transferring Output" and "Suspended" states. 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. input this into any Python Aviary client tmp = client.factory.create("ns0:JobID") print tmp Actual results: (ns0:JobStatusType){ IDLE = "IDLE" RUNNING = "RUNNING" REMOVED = "REMOVED" COMPLETED = "COMPLETED" HELD = "HELD" } Expected results: (ns0:JobStatusType){ IDLE = "IDLE" RUNNING = "RUNNING" REMOVED = "REMOVED" COMPLETED = "COMPLETED" HELD = "HELD" TRANSFERRING = "TRANSFERRING" SUSPENDED = "SUSPENDED" }
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: Aviary XML schema for the various job states. Consequence: There are no states listed for suspended and transferring_output jobs in the JobStatusType. Change: The Aviary XML schema was updated to add these new job states. Implementation changes were made to reflect these totals in the API also. Result: Aviary clients can view the totals for suspended and transferring_output job states from this XML schema type.
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