cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4442) Source NAT not applied when network starts up
Date Thu, 22 Aug 2013 07:10:55 GMT


ASF subversion and git services commented on CLOUDSTACK-4442:

Commit 197108c6a344a043ef3394859e8f341fd3de138b in branch refs/heads/master from [~tsp]
[;h=197108c ]

CLOUDSTACK-4442: Include a test for creating networks with sourcenat only

The test attempts to create a network with offering serving only
dhcp,dns and sourcenat. However the source NAT functionality itself
isn't tested as reported in the bug. So the test will pass.

TODO: come up with a way to test source nat without enabling additional
services for pf/staticnat

Signed-off-by: Prasanna Santhanam <>
(cherry picked from commit 79df10ee24840dc7fe8fdb4ccbde240658a109fc)

> Source NAT not applied when network starts up
> ---------------------------------------------
>                 Key: CLOUDSTACK-4442
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Devices
>    Affects Versions: 4.2.0
>            Reporter: Dave Cahill
>            Priority: Blocker
>             Fix For: 4.2.0
> Create a network with Source NAT but no static NAT, and no firewall rules applied.
> Observed behavior:
> Source NAT is not applied when the first VM is launched (when network is implemented)
> Expected:
> Source NAT enabled at network implement time
> Network devices:
> Should affect all network devices; verified in 2 separate environments, one with Virtual
Router only, one MidoNet only
> Further information:
> This bug seems to be a result of this change:
> The above change was made as a fix for CLOUDSTACK-234.
> If the user enables Static NAT, Source NAT will be applied as a side effect.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message