This is my third post on the subject, but I'd like to see if anyone on the list who is running 14.11.3 or later can reproduce. We upgraded to 14.11.7 on Tuesday, but the problem hasn't gone away. Below are the simple steps to reproduce:
1. Create a reservation for right now on a free node in a partition scontrol create reservation=test1 StartTime=now Duration=2:00:00 Partition=osu NodeCnt=1 flags=DAILY Users=bbarth 2. Create a reservation for 24 hours later on one node in the same partition: scontrol create reservation=test2 StartTime=2015-07-16T13:30:00 Duration=2:00:00 Partition=osu NodeCnt=1 Users=bbarth These reservations select the same node in my experience, because test2 does not appear to take into account the fact that the node could be used by test1 the next day. Come today, the reservations now overlap. FWIW, this is exactly what scontrol show res showed during right after creation yesterday, except that test1 was listed as ACTIVE. ReservationName=test1 StartTime=2015-07-16T13:18:39 EndTime=2015-07-16T15:18:39 Duration=02:00:00 Nodes=c445-001 NodeCnt=1 CoreCnt=8 Features=(null) PartitionName=osu Flags=DAILY Users=bbarth Accounts=(null) Licenses=(null) State=INACTIVE ReservationName=test2 StartTime=2015-07-16T13:30:00 EndTime=2015-07-16T15:30:00 Duration=02:00:00 Nodes=c445-001 NodeCnt=1 CoreCnt=8 Features=(null) PartitionName=osu Flags= Users=bbarth Accounts=(null) Licenses=(null) State=INACTIVE I would be much obliged if someone out there would test this on their recent SLURM system to see if they can reproduce the problem. I intend to test this on our SLURM test set of VMs with a fresh 14.11.7 installation as well, but I wanted to get this message out immediately first while we're setting up that test. Has anyone else seen this? Thanks, Bill. -- Bill Barth, Ph.D., Director, HPC [email protected] | Phone: (512) 232-7069 Office: ROC 1.435 | Fax: (512) 475-9445
