cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2319) 2.2.14 to 4.1.0 upgrade: unable to add egress rules
Date Mon, 02 Sep 2013 14:55:52 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756122#comment-13756122
] 

ASF subversion and git services commented on CLOUDSTACK-2319:
-------------------------------------------------------------

Commit 62b09c9253a4a942f0e0b6649b87e18d4bc70464 in branch refs/heads/master from [~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=62b09c9 ]

CLOUDSTACK-2319: fix incorrect account_id in event table for Revoke SecurityGroupRule commands
(cherry picked from commit d9ba234d6c032aeb2ba04d4e6be0502de8a4efd9)

                
> 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
>            Assignee: Wei Zhou
>            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 with no rules by default.
> This causes the VM to stop connecting to the outside world, and the traffic is one way.
> I can SSH to the VM, and  I can ping the VM , but I cannot ssh or ping from the VM. 
> 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 in the management log. 
> Notes: 
> Upgrade Environment:  CloudStack 2.2.14, Advance Networking with Security Groups, CentOS
6.4
> There were no issues during the upgrade process. All steps completed successfully. 
> The system VMs were upgraded successfully 
> ----------------------------------------------------------------------
> Stopping and starting 1 secondary storage vm(s)...
> Done stopping and starting secondary storage vm(s)
> Stopping and starting 1 console proxy vm(s)...
> Done stopping and starting console proxy vm(s).
> Stopping and starting 1 running routing vm(s)...
> Done restarting router(s).
> ----------------------------------------------------------------------

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