You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alexander Conn (JIRA)" <ji...@apache.org> on 2018/01/17 06:54:00 UTC
[jira] [Created] (CLOUDSTACK-10235) Removing Port Forwarding rule
deletes public interface on VR (redundant VPC only)
Alexander Conn created CLOUDSTACK-10235:
-------------------------------------------
Summary: 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
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)