Dave Cahill created CLOUDSTACK-4442:
---------------------------------------
Summary: Source NAT not applied when network starts up
Key: CLOUDSTACK-4442
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4442
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:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blobdiff;f=server/src/com/cloud/network/NetworkManagerImpl.java;h=2b53565297dc7bd96c6102cdc1c90cb166e9e704;hp=dac6a3a42e75324a963997e17e076f4020a7103e;hb=fe568fe;hpb=c7f26583a26eb7e4f15feafc292ec9576df61a8d
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: http://www.atlassian.com/software/jira
