I tried that already by leaving the field blank as in "flags=" but that has no effect. Should I change it to something else?
Glen On Apr 15, 2016 10:16 AM, "Carlos Fenoy" <mini...@gmail.com> wrote: Hi Glen, I think your issue is with the MAINT flag in the reservation. Try removing that flag and try again. Regards, Carlos On Fri, Apr 15, 2016 at 4:09 PM, Glen MacLachlan <macl...@gwu.edu> wrote: > Dear all, > > Wrapping up a maintenance period and I want to run some test jobs before I > release the reservation and allow regular user jobs to start running. I've > modified the reservation to allow jobs from my account: > > $ scontrol show res > ReservationName=root_13 StartTime=2016-04-12T09:00:00 > EndTime=2016-04-15T20:00:00 Duration=3-11:00:00 > Nodes=ALL NodeCnt=220 CoreCnt=3328 Features=(null) PartitionName=(null) > Flags=MAINT,SPEC_NODES > TRES=cpu=3328 > Users=bindatype Accounts=(null) Licenses=(null) State=ACTIVE > BurstBuffer=(null) Watts=n/a > > > but when I try to allocate a set of nodes I keep seeing the following: > > $ salloc -p defq -t 10 > salloc: Required node not available (down, drained or reserved) > salloc: Pending job allocation 1692921 > salloc: job 1692921 queued and waiting for resources > > > Note that all the nodes are currently in the maint state. Am I missing > something here or is this a problem with scontrol update? > > > > -- -- Carles Fenoy
