cloudstack-issues mailing list archives

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


ASF GitHub Bot commented on CLOUDSTACK-9437:

Github user swill commented on the issue:
    I manually merged this into `master` (`d302269fe53ca0d3ef4c7d4c51b28ce94d8a4847`) because
there were merge conflicts and I could not do it through `git pr`, so you can close this PR

> Outbound traffic fails to work after VR is upgraded to post 4.6+ release
> ------------------------------------------------------------------------
>                 Key: CLOUDSTACK-9437
>                 URL:
>             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
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

View raw message