[
https://issues.apache.org/jira/browse/VCL-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Kurth updated VCL-322:
---------------------------
Fix Version/s: 2.4
> Add code to check that the static public address is set for all new/reload
> reservations, even if computer is not reloaded
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: VCL-322
> URL: https://issues.apache.org/jira/browse/VCL-322
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Affects Versions: 2.1
> Reporter: Andy Kurth
> Priority: Minor
> Fix For: 2.4
>
>
> If static public IP addresses are used, an attempt is only made to set the
> address if the computer is reloaded. If a computer is preloaded, the static
> address is not set because it's assumed it was set the last time it was
> reloaded. There is no code to check to make sure the static address is
> correct if the computer does not need to be reloaded.
> This causes an endless problem if the static address failed to be set during
> the last reservation where the computer was reloaded. If it fails, the
> reload reservation fails and the computer state is set to failed (correct
> behavior). If the computer state is set to available, user reservations will
> timeout over and over again because the user can't connect (the public IP
> address is incorrect). This happens because sshd and the currentimage.txt
> file are both correct, so a reload is not performed.
> Log output from an example of this problem:
> The original reload failed trying to set the static address:
> 2010-02-13
> 23:41:02|11728|846519:920517|reload|utils.pm:run_ssh_command(6167)|executing
> SSH command on evm1-190:
> |11728|846519:920517|reload| /usr/bin/ssh -i /etc/vcl/bladekey -i
> /etc/vcl/winxp_blade.key -i /etc/vcl/bladelinuxkey_id_rsa -l root -p 22 -x
> evm1-190
> '$SYSTEMROOT/System32/ipconfig.exe /all' 2>&1
> |11728|846519:920517|reload| ---- WARNING ----
> |11728|846519:920517|reload| 2010-02-13
> 23:41:03|11728|846519:920517|reload|Windows.pm:get_network_configuration(4715)|failed
> to run ipconfig, exit st
> atus: 5, output:
> |11728|846519:920517|reload| none
> |11728|846519:920517|reload| ( 0) utils.pm, notify (line: 727)
> |11728|846519:920517|reload| (-1) Windows.pm, get_network_configuration
> (line: 4715)
> |11728|846519:920517|reload| (-2) Windows.pm, get_public_interface_name
> (line: 4948)
> |11728|846519:920517|reload| (-3) Windows.pm, set_static_public_address
> (line: 7451)
> |11728|846519:920517|reload| (-4) vmware.pm, load (line: 1076)
> |11728|846519:920517|reload| (-5) new.pm, reload_image (line: 665)
> |11728|846519:920517|reload| (-6) new.pm, process (line: 266)
> Subsequent reservations were not reloaded. The auto-assigned IP address was
> set on the computer:
> 2010-02-16
> 15:16:18|31327|850062:924070|deleted|Windows.pm:get_network_configuration(4824)|private
> interface found: Local Area Connection, description: AMD PCNET Family PCI
> Ethernet Adapter #5, address(es): 172.22.2.190
> 2010-02-16
> 15:16:18|31327|850062:924070|deleted|Windows.pm:get_network_configuration(4872)|public
> interface found: Local Area Connection 2, description: AMD PCNET Family PCI
> Ethernet Adapter #6, address(es): 169.254.229.120
> 2 (169.254.229.120)
> Several reservations were assigned to this computer and timed out because the
> user could not connect to the 169.254 address.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
