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

Alexander Conn commented on CLOUDSTACK-10235:
---------------------------------------------

Ok I can see this is being done by the management server: 

2018-01-19 13:33:43,263 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-413:ctx-e3bdcca3) (logid:0268a127) Executing command in VR: 
/opt/cloud/bin/router_proxy.sh netusage.sh 169.254.1.201 -d eth1

 

Which is handled by this function: protected ExecutionResult 
cleanupNetworkElementCommand
file: 
[https://github.com/apache/cloudstack/blob/a30a31c9b7f9b5fe246a02285bf820e7fe9ce16e/plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java]

For whatever reason, it thinks that the IP used for port forwarding is the last 
IP for whatever reason and as a result deletes the public interface. Need to 
further investigate why...

 

> Removing Port Forwarding rule deletes public interface on VR (redundant VPC 
> only)
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10235
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10235
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: VPC
>    Affects Versions: 4.9.3.0
>         Environment: XenServer 6.2
>            Reporter: Alexander Conn
>            Priority: Critical
>
> Steps I've taken to reproduce in my environment on a redundant VPC (no issue 
> on normal VPC):
>  # Acquire public IP and create a port forwarding rule on it
>  # Remove that port forwarding rule
>  # You'll see on the MASTER VR, the public interface (eth1) gets removed 
> incorrectly. Causing all sorts of issues, including issues with VRRP.
>  # Add a port forwarding rule back, and eth1 gets recreated. But now your 
> stuck with needing at least 1 PF rule to be there in order to keep eth1 
> connected.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to