I figured out the cause of this problem. It was actually due to the improvement 
provided in 2.2.1, where the management node pays attention to the memory of 
the vmhost and won't overbook the memory if a reservation would do so.

The RAM setting of the vmhost in the computer table was 1Gb (it really has 
16Gb). It was allowing a reservation for the XP image because its profile had a 
memory setting of 1Gb. It was not allowing a reservation for the RHEL-5 image 
because its profile had a memory setting of 2Gb. Once I updated the vmhost 
memory setting to 16Gb, it would allow reservations for the RHEL-5 image.


Mike Waldron
Systems Specialist
ITS Research Computing
University of North Carolina at Chapel Hill
CB 3420, ITS Manning, Rm 2509
919-962-9778


-----Original Message-----
From: Waldron, Michael H [mailto:mwald...@email.unc.edu] 
Sent: Tuesday, May 10, 2011 1:51 PM
To: 'vcl-dev@incubator.apache.org'
Subject: Problem with 2.2.1 upgrade

I have a VCL 2.2 sandbox installation that I updated to 2.2.1, and I'm seeing a 
strange problem that I haven't been able to figure out.

There are 2 base images in the sandbox, a Windows XP image, and a RHEL-5 image. 
Immediately prior to the 2.2.1 update, I can select either image to make a Now 
reservation. Immediately after the update,  I can still select the XP image for 
a Now reservation, however when I select the RHEL-5 image, I get the message 
"Selection not currently available", and it displays the "View Time Table" 
button.

If I click the "View Time Table" button, all times show green (available). 
Whenever I select any of them, I still get the message "Selection not currently 
available". If I choose a Later reservation, any time I select it tells me that 
time is not available.

Both of these images belong to the same image group mapped to the same computer 
group. So I can't figure out why it will let me reserve the XP image but not 
the RHEL-5 image. I reloaded the sandbox image to its fresh 2.2 state, and 
verified that I could reserve both images, then repeated the 2.2.1 upgrade 
process, and again I have the same issue where I can reserve the XP image but 
not the  RHEL-5 image. So something with the 2.2.1 upgrade is causing the issue.

Mike Waldron
Systems Specialist
ITS Research Computing
University of North Carolina at Chapel Hill
CB 3420, ITS Manning, Rm 2509
919-962-9778

Reply via email to