cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashi Dahal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-2319) 2.2.14 to 4.1.0 upgrade: unable to add egress rules
Date Fri, 03 May 2013 09:36:15 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shashi Dahal updated CLOUDSTACK-2319:
-------------------------------------

    Labels: egress kvm security-groups upgrade  (was: )
    
> 2.2.14 to 4.1.0 upgrade: unable to add egress rules
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-2319
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2319
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.1.0
>            Reporter: Shashi Dahal
>            Priority: Blocker
>              Labels: egress, kvm, security-groups, upgrade
>             Fix For: 4.1.0
>
>
> Hi, 
> For VMS that are running when in 2.2.14 and when upgraded to 4.1.0, they are unable to
connect outside. 
> This is because egress rules are introduced which are not added by default. 
> This causes the VM to stop connecting to the outside working, and the traffic is one
way.
> I am unable to add egress rules and there is not even a single line showing the api calls
or anything related to adding the egress rules.  So on the management server, I see  it waiting
to add the rules, but no corresponding lines in management log to give  you any idea of why
it is failing. 

--
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

Mime
View raw message