Hello, We have a full scale reservation today (again). The user submitted a job, then sometime after a node was marked down and slurmctld came up with a new list of a nodes for the reservation. The pending jobs that were already submitted were not able to run with reason "Reservation". New jobs could start. In the end I ended up updating the time limit of the job and it started (and then updated the time limit back). My guess is that the job update caused the reservation data structure in slurmctld to be re-evaluated allowing the job to run. I'm presupposing that the nodelist update may have invalidated a pointer or other reference to the reservation for the preexisting pending job. Thanks, Doug
Hi I can't recreate this. Could you send us slurmctld.log and output from 'scontrol show res'? Dominik
Hi Any news? Dominik
Hi Doug, Could you send me slurmctld.log containing this situation? Could you describe how you created this reservation? Thanks Dominik
Hi Doug, I know you are busy, but I need more info to move on with this. Dominik
Hi This is the last call :) Dominik
I am closing this as timedout. Please,reopen if needed. Dominik