You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/05/18 20:18:04 UTC

[jira] [Commented] (VCL-1048) NAT rules not always deleted when a reservation ends

    [ https://issues.apache.org/jira/browse/VCL-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016400#comment-16016400 ] 

ASF subversion and git services commented on VCL-1048:
------------------------------------------------------

Commit 1795558 from arkurth@apache.org in branch 'vcl/trunk'
[ https://svn.apache.org/r1795558 ]

VCL-1048
Replaced calls in image.pm from legacy utils.pm::switch_state to state_exit and removed explicit calls to exit.

Renamed iptables.pm::sanitize_nat_reservation to nat_sanitize_reservation to match format of other NAT subroutines.

Added code to State.pm::state_exit to call nat_sanitize_reservation if NAT is used and (argument was passed to set log.ending or the next request state is (timeout|deleted|complete|image|checkpoint).

Removed call to sanitize_nat_reservation from reclaim.pm::process.

> NAT rules not always deleted when a reservation ends
> ----------------------------------------------------
>
>                 Key: VCL-1048
>                 URL: https://issues.apache.org/jira/browse/VCL-1048
>             Project: VCL
>          Issue Type: Bug
>          Components: vcld (backend)
>    Affects Versions: 2.4.2
>            Reporter: Andy Kurth
>            Assignee: Andy Kurth
>             Fix For: 2.5
>
>
> There are a few conditions where the rules created for a reservation aren't being deleted on the NAT host when a reservation ends.  The sanitize_nat_reservation subroutine is being called from reclaim.pm::process.  This doesn't always get called.  For example, imaging reservations execute image.pm::process, insert a reload reservation, then directly exit.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)