+++ This bug was initially created as a clone of Bug #221228 +++
Description of problem:
Sometimes the reservesys installation EWD-timeouts. I found out it is best to
schedule the same installation/reservation multiple times as one of the machines
may succeed. If you wait till it Aborts you will get the same incompatible
combination scheduled during the retr
also, you can randomize your machine choice by changing the following in your xml:
but there is no web UI for this in the reserve_workflow. It'd be nice to get it
exposed there too, not just job-cloning.
*** Bug 221228 has been marked as a duplicate of this bug. ***
I do not understand what random="false" can ever be good for.
(In reply to comment #2)
Ordinarily Beaker orders candidate systems by some heuristics that are theoretically good for overall scheduling performance -- selecting private systems before ones from the public pool. Setting <autopick random="true" /> defeats that, so it is not enabled by default.
The scheduler's behaviour in this regard is slated to be improved as part of the upcoming "groups model" enhancements anyway.