Yeah, something is not working right. Even though I removed the block allocation, it still reloaded the machines at the block allocation time because the entries were never removed from the database. Any ideas?
David DeMizio *Academic Systems Coordinator* Office of Information Technology New College of Florida Phone: 941-487-4222 | Fax: 941-487-4356 www.ncf.edu On Wed, Dec 4, 2013 at 8:24 AM, David DeMizio <[email protected]> wrote: > Hello, > > I'm testing block allocations at the moment so I set up two schedules: > > 1) has 5 seats from 8:15 - 8:45 - Linux image > 2) has 4 seats from 9:00 - 9:30 - Windows image > > I have 6 computers total. I received the error below after I modified the > group that could create the reservation on the block allocation. Why am I > getting unable to allocate machines when the start time of Windows image is > 9:00 a.m? Also, when making changes to the allocation does it attempt to > reload the machines? I would think that as long as I don't change the image > to load that it would leave the machines untouched. Thank You > > > |20610|blockrequest| ---- CRITICAL ---- > |20610|blockrequest| 2013-12-04 > 08:14:05|20610|blockrequest|blockrequest.pm:process(245)|Problem > processing block allocation > |20610|blockrequest| Block id = 4 > |20610|blockrequest| Block name = test2 > |20610|blockrequest| Block start time = 2013-12-04 09:00:00 > |20610|blockrequest| Block end time = 2013-12-04 09:30:00 > |20610|blockrequest| Environment name = Windows 7 64Bit > |20610|blockrequest| Allocated = 1 > |20610|blockrequest| Block requested = 4 > |20610|blockrequest| xmlrpc warn msg = unable to allocate any machines > |20610|blockrequest| ( 0) blockrequest.pm, process (line: 245) > |20610|blockrequest| (-1) vcld, make_new_child (line: 571) > |20610|blockrequest| (-2) vcld, main (line: 451) > > >
