GitLab

This can happen from some of the XMLRPC calls.

In light of this bug, adding checks to make sure that we don't end up
accidentally adding in bad values to reservations again.

This could happen when the node goes down while a job is running,
causing the node to still show up in the job end_times.

Backfillng has an epsilon of 2 minutes by default.  This can be altered
in the cobalt config file.

There was a way to set up resrvations across disjoint queues that caused
one set of queues to ignore that a reservation was pending because the
reservation wasn't associated with that equivalence class.  This caused
forbidden locations to not be set.

Draining and backfilling are passing basic tests.  Need to add more test
cases to the automated suite and test corner cases around
queues/reservations/locations list.

Also need to add backfill time display to nodelist/nodeadm -l.

Checking in fixes for find queue equivalence classes that impact
draining.  Drain-status-clear now working.  Stub for drain selection.

Thanks Eric!  Duplicated nids are now avoided.

Fixes attrs location evading cobalt admin down on nodes.

Non-idle nodes are now fully respected.  Consistiently get string nid
lists out of this.  ValueError doesn't get raised if the attrs location
exists stradling a reservation (still in the queue, but not available
due to the reservation).