Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
1.12.8
-
None
Description
Current Situation
- How to reproduce
- The ./live folder contains a sub-directory, e.g. ./live/js-1827, with a job chain. The contents of the job chain configuration is irrelevant to reproduce this problem.
- The web service http://host:port/jobscheduler/master/api/job?return=JocOrderStatistics&isDistributed=false with Body:
{"path":"/"}
returns the list of jobs that are available from the ./live folder:
/js-1827/job: due: 0 notPlanned: 0 setback: 0 inTask: 0 waitingForResource: 0 suspended: 0 total: 0 occupiedByClusterMember: 0 permanent: 0 planned: 0 inTaskProcess: 0 blacklisted: 0 started: 0 fileOrder: 0 /scheduler_file_order_sink: due: 0 notPlanned: 0 setback: 0 inTask: 0 waitingForResource: 0 suspended: 0 total: 0 occupiedByClusterMember: 0 permanent: 0 h3. Desired Behavior planned: 0 inTaskProcess: 0 blacklisted: 0 started: 0 fileOrder: 0 /scheduler_service_forwarder: due: 0 notPlanned: 0 setback: 0 inTask: 0 waitingForResource: 0 suspended: 0 total: 0 occupiedByClusterMember: 0 permanent: 0 planned: 0 inTaskProcess: 0 blacklisted: 0 started: 0 fileOrder: 0
- Remove the job chain from the sub-directory ./live/js-1827
- The return of the web service http://host:port/jobscheduler/master/api/job?return=JocOrderStatistics&isDistributed=false is now
SCHEDULER-161 There is no JobChain '.'
- Delimitation
- This problem occurs with job chains from sub-directories of the ./live folder, it does not occur for job chains that are located in the ./live folder.
Desired Behavior
- The web service http://host:port/jobscheduler/master/api/job?return=JocOrderStatistics&isDistributed=false should always return the list of available jobs, independent from the fact that previously an arbitrary job chain configuration file has been removed.