[
https://issues.apache.org/jira/browse/CLOUDSTACK-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745901#comment-13745901
]
ASF subversion and git services commented on CLOUDSTACK-4418:
-------------------------------------------------------------
Commit 81b5146c8ed1a590b08b71a3e3421966974b74f9 in branch refs/heads/4.2 from
[~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=81b5146 ]
CLOUDSTACK-4418: allow egress access to all networks for VMs on NAT
Tests doing operations within guests post VirtualMachine.create w. default
network offering fail since the egress policy with isolated networks and
sourcenat services is DENY.
Signed-off-by: Prasanna Santhanam <[email protected]>
> Tests doing operations within guests post VirtualMachine.create w. default
> network offering fail
> ------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4418
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4418
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Reporter: Prasanna Santhanam
> Assignee: Prasanna Santhanam
> Priority: Critical
>
> Tests typically will call on VirtualMachine.create() with no networkids
> passed.
> In such cases the VM is deployed using a network created by the "Default"
> offerings (Isolated with SourceNAT). These offerings with 4.2 by default DENY
> all outgoing traffic until egress rules are added to allow access.
> This causes all tests doing deployVM without networkid to fail when there are
> guest operations like wget done within the VMs
--
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
