Hide Forgot
Description of problem: If Aviary is used to submit multiple jobs under the same submission name and then to delete one of the jobs, the QMF submission object is deleted even though there are still jobs running in the submission. This only appears to happen when the schedd is publishing submissions (QMF_PUBLISH_SUBMISSIONS = True and there is no JOB_SERVER daemon). Version-Release number of selected component (if applicable): condor-aviary-7.7.3-0.2.fc16.x86_64 condor-7.7.3-0.2.fc16.x86_64 condor-qmf-7.7.3-0.2.fc16.x86_64 How reproducible: 100% Steps to Reproduce: 1. Clean install of personal condor with no job history. Did this on a machine with 4 slots. 2. Modify /usr/share/condor/aviary/submit.py so that job duration is long enough to test (change 120 seconds to 1d, for example) 3. Submit some number of jobs $ /usr/share/condor/aviary/submit.py $ /usr/share/condor/aviary/submit.py $ /usr/share/condor/aviary/submit.py 4. Run qpid-tool, look for the submission. Leave qpid-tool open. 5. $ /usr/share/condor/aviary/jobcontrol.py --cmd=removeJob --cproc=1.0 6. Look for the submission again in qpid-tool. It will be marked as deleted. Start a new qpid-tool and verify that the object is not there. 7. See the submission through aviary, verify with condor_q $ /usr/share/condor/aviary/submissions.py $ condor_q Actual results: QMF object is deleted when a single job is deleted, aviary and condor_q show the jobs/submission correctly. Expected results: QMF object will remain while there are running jobs. Additional info: QMF object appears to come back if /usr/share/condor/aviary/submit.py is run again, but the total removed/running count is off. Of course, the submission will also come back if condor is restarted.
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.