Uploaded image for project: 'JOC - JobScheduler Operations Center'
  1. JOC - JobScheduler Operations Center
  2. JOC-488

For nested job chains <modify_hot_folder/> command on order creates an extra order

    XMLWordPrintable

Details

    Description

      Current Situation

      • A nested job chain "nested_chain" is configured with two job chains e.g., job_chain1, job_chain2
      • An order is configured to start the nested job chain e.g. nested_chain,start.order.xml
      • The order nested_chain,start.order.xml references a schedule, e.g. schedule1
        <?xml version="1.0" encoding="ISO-8859-1"?>
        <order  title="test" job_chain="nested_chain" id="start">
            <params />
            <run_time  schedule="schedule1"/>
        </order>
        
      • If a user removes the schedule1 from the order using JOC Cockpit --> "Set Run-time" action menu and "Remove Schedule" operation then the order will be updated by a <modify_hot_folder> command. The following three behaviors are observed:
        1. a new order is created job_chain1,start.order.xml
        2. the order nested_chain,start.order.xml is not modified
        3. In the JOC Cockpit the order nested_chain,start.order.xml is visible but no "show configuration" option is available or when clicking the "Set Run-time" action then a JOC-420 error is thrown like this:
          JOC-400
          JobSchedulerBadRequestException: SCHEDULER-162 There is no order start in job chain "/support/Ticket#2018080910000015/test/nested_chain 

      Desired Behavior

      • Removing a schedule from an order for a nested job chain should not create an extra order and should be available from the JOC Cockpit.

      Attachments

        Activity

          People

            oh Oliver Haufe
            mp Mahendra Patidar
            Mahendra Patidar Mahendra Patidar
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: