Cisco Bug: CSCvh77860 - Active Unix Agent jobs set to Hold/Stop have inconsistant outcomes when releasing stop
Feb 02, 2018
- Cisco Workload Automation
Known Affected Releases
Symptom: A Unix Agent job can be set to stopped by using Hold/Stop. The Process continues to run on the Unix Agent server. The Process appears to run but continues to take a slot in the queue until Release/Resume is used and the job is released and gets a Status of Completed Normally. Conditions: 6.2.1/6.3.1 1. Create a sleep job with command parameter of 100. 2. Insert the job into the schedule and wait for it to go Active. 3. Right Click on job and go to Job Control, Hold/Stop. 4. Observe that the status is now stopped. 5. On the Unix Agent server you will see the Process is still running. 6. You can observe in the System Queue that the job is still taking a slot. 7. After 2 minutes in Job Control choose Release/Resume. 8. Job goes to Completed Normally immediately instead of completely the time of 100. 9. Observe in the history tabl of the jobrun that duration is 1 sec. Complete steps 1 - 6 above. 1. Select release/renew before the 100 seconds have passed. 2. Observe job goes active but does not equal the 100 seconds the job was to run.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases