[
https://issues.apache.org/jira/browse/VCL-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340236#comment-15340236
]
ASF subversion and git services commented on VCL-940:
-----------------------------------------------------
Commit 1749392 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1749392 ]
VCL-940
Added OS.pm::wait_for_public_ip_address. This gets called from
OS.pm::update_public_ip_address.
Added $no_cache and $ignore_error arguments to several get_* networking
subroutines to allow fresh data to be retrieves and to suppress warning
messages.
Removed Windows.pm::get_public_interface_name and get_public_ip_address. These
were already looping until the public IP was obtained. Having everything use
the code in OS.pm is simpler.
> timing issue getting public IP
> ------------------------------
>
> Key: VCL-940
> URL: https://issues.apache.org/jira/browse/VCL-940
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Reporter: Josh Thompson
> Assignee: Andy Kurth
>
> I saw a condition with an Ubuntu based image where vcld failed to get the
> public IP address because it had not yet been assigned. The dhcpd server
> handed out the address one second before vcld added an entry to vcld.log
> about trying to get the public IP address and then not seeing it set.
> Likely, the node had the address but had not finished setting it on the NIC.
> This probably was never a problem with sysv but with systemd, things can
> happen in parallel enough that the timing doesn't work out. Adding something
> such as a sleep and a 2nd try at getting the address would probably fix the
> problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
