The problem turned out to be that I had the memory setting too low on the
vmhost. The VCL was correctly recognizing based on that number that there was
insufficient memory available to load the RHEL-5 image which requested more
memory than available. After adjusting the memory setting on the vmhost to
reflect reality, things worked fine.
ITS Research Computing
University of North Carolina at Chapel Hill
CB 3420, ITS Manning, Rm 2509
From: Josh Thompson [mailto:jftho...@ncsu.edu]
Sent: Tuesday, May 10, 2011 3:25 PM
Subject: Re: Problem with 2.2.1 upgrade
Try commenting out lines 3720 through 3734 in utils.php. That is a
block of code I added to attempt detection of failed computers that
were missed by the backend. I have seen a few corner cases where it
doesn't behave as expected. The main thing being that it should
always leave at least one computer in the list of available computers.
If commenting it out works for you, you can safely leave it commented
On Tue, May 10, 2011 at 1:51 PM, Waldron, Michael H
> 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