I think I found the problem. Edit this file:
/usr/local/vcl/lib/VCL/Module/OS/Linux/Ubuntu.pm
Find this line, it should be around line number 789:
notify($ERRORS{'OK'}, 0, "successfully set static public IP address on
$computer_name");
Add this line before the line you found:
delete $self->{network_configuration};
Save the file and run 'service vcld restart'. This should fix the
problem. The network configuration had been retrieved before the static
public IP address was getting set and this information was cached. The
Ubuntu.pm module wasn't erasing the cache after it changed the network
settings. This is already fixed in the upcoming version of VCL. You
shouldn't have this problem for other non-Ubuntu Linux and Windows images.
Regards,
Andy
On Thu, Jul 28, 2016 at 11:25 AM, Doran,William <[email protected]> wrote:
> Hello,
> I recently began working on bringing up a new instance of VCL using the
> latest stable release (2.4.2). Josh was very helpful in providing
> directions for transferring the images from our older version of VCL to
> this new one. However, I'm having some problems loading the VMs with these
> images. Sometimes they work fine, and other times, I have to reload
> several times until it finally completes successfully. When they fail, it
> indicates that VCL is unable to determine the public ip address (even
> though VCL is statically setting this and I have been able to log into the
> VMs via the Vsphere console and see that both the private and public ip
> addresses are indeed assigned to the NICs and working). There is no common
> factor that I can find, for instance, the same VM that fails several times
> in a row will finally work at one point, until I reload it again (so I
> don't think its an issue with how I have the VM computers configured in
> VCL). I'm using Centos v7 on the management and web nodes, and ESXi 6 for
> the VM hosts. Attached is the log from a recent load attempt that failed
> ("OS.pm:get_ip_address|1927|unable to determine public IP address,
> 'ip_address' value is not set in the network configuration info"). Does
> anyone have any suggestions on what may be the cause/problem and how to
> resolve this?
>
> Thanks in advance!
> -Bill
>
>
