cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9437) Outbound traffic fails to work after VR is upgraded to post 4.6+ release
Date Tue, 26 Jul 2016 05:13:20 GMT

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

ASF GitHub Bot commented on CLOUDSTACK-9437:
--------------------------------------------

Github user rhtyd commented on the issue:

    https://github.com/apache/cloudstack/pull/1614
  
    Alright Will, closing now.


> Outbound traffic fails to work after VR is upgraded to post 4.6+ release
> ------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9437
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9437
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.6.2, 4.7.1, 4.8.0, 4.8.1
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Blocker
>
> When CloudStack is upgraded to 4.6+ version, due to changes in script. The default iptables
rules are saved at /etc/iptables/router_rules.{v4,v6} instead of the rules.{v4,v6} files.
The cloud-early-config file uses the rules.v4 and rules file, which are copied from iptables-{router,
etc.} templates.
> When CloudStack was upgrade from 4.3 to 4.6+ version, and VR template upgraded to a 4.6
template -- the rules.v4 file was copied from iptables-router template though the configure.py
uses router_rules.v4 file which does not have the FW_EGRESS_RULES chain declared. Because
of this the CsNetFilters fails to add the chain.
> Workaround that works -- after upgrading the router, restarting the network (without
cleanup selected) fixes the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message