[
https://issues.apache.org/jira/browse/CLOUDSTACK-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748475#comment-13748475
]
ASF subversion and git services commented on CLOUDSTACK-4418:
-------------------------------------------------------------
Commit e39156e4d6f572bbfaf08c7f3ccf2d99bee0b5e1 in branch
refs/heads/4.2-forward from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e39156e ]
CLOUDSTACK-4473: allow_egress referenced before assignment
When deploying with networkids allow_egress gets no default value. This
is a regression caused by fix for CLOUDSTACK-4418
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
