Hello, I had a failed reservation last night and the problem is related to an already assigned VM being assigned to a new reservation. The VM " vcl-vm-17" that was originally assigned to reservation # 16698 and then a new reservation (# 16699) came in that tried to use the same VM and failed. It looks like reservation # 16698 was not acknowledged by the user and eventually timed-out, but this was after the reservation # 16699 had failed.
Any ideas why VCL is trying to assign a busy VM to another reservation? The version of VCL is 2.2.1 VCLD log is available at: http://pastebin.com/WH1Srwuj Thanks. Junaid Ali
